PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-76233 renovatebot CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-19T14:17:50.957Z and has not been modified since then. This command injection vulnerability in Renovate versions from 39.53.0 before 40.33.0 allows attackers with repository write access to execute arbitrary commands via crafted gleam.toml files. Defenders should assess exposure, especially in environments where repository write access is a concern, and prioritize verification of Renovate installations.

Vendor
renovatebot
Product
renovate
CVSS
HIGH 8.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-19
Original CVE updated
2026-09-08
Advisory published
2026-08-19
Advisory updated
2026-09-08

Who should care

Defenders responsible for Renovate installations, especially in environments where repository write access is a concern, should assess exposure to this command injection vulnerability.

Why it matters

Defenders should prioritize verifying exposure of Renovate installations to this command injection vulnerability, especially in environments where repository write access is a concern. The vulnerability allows attackers to execute arbitrary commands, making it a high-severity issue.

  • Potential execution of arbitrary commands on the machine running Renovate
  • Possible malicious activity through crafted gleam.toml files
  • Verification of Renovate version and exposure to this vulnerability

Technical summary

Renovate versions from 39.53.0 before 40.33.0 contain a command injection vulnerability in the gleam manager. The depName parameter is appended to gleam deps update commands without proper sanitization, allowing attackers with repository write access to craft malicious gleam.toml files and execute arbitrary commands. This vulnerability is a high-severity issue, with potential for significant operational impact if exploited. Defenders should prioritize verifying exposure of Renovate installations, especially in environments where repository write access is a concern.

Defensive priority

Defenders should prioritize verifying exposure of Renovate installations to this command injection vulnerability, especially in environments where repository write access is a concern.

Recommended defensive actions

  • Verify Renovate installations for exposure to this command injection vulnerability
  • Update Renovate to version 40.33.0 or later
  • Monitor repository write access and gleam.toml files for potential malicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the command injection vulnerability in Renovate versions before 40.33.0. The vulnerability is in the gleam manager where the depName parameter is not properly sanitized.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-76233 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-76233

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-76233 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76233

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.