CVE-2026-70551
Read-only VCS access can replace repo origin or supply an absolute VCS URL.
Is CVE-2026-70551 being exploited?
Not confirmed. CVE-2026-70551 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-70551?
CVE-2026-70551 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-70551?
Not known from our data. No patch reference has been recorded for CVE-2026-70551, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-70551 affect?
CVE-2026-70551 affects Version control systems (Git/Mercurial), CI/CD servers and build agents, Repository hosting services, Automated build/deploy pipelines, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70551?
Restrict repo read permissions; audit and lock origins in CI; block external/absolute VCS URLs; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with read access can redirect repo origin to attacker-controlled or data URLs, enabling supply-chain code injection, SSRF, arbitrary code fetch and possible RCE during automated builds.
Immediate action required
- affected>= 7.161.0 and < 7.161.19
- affected>= 7.146.0 and < 7.146.36
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.