CVE-2026-66375
Authenticated low‑privilege user can permanently delete protected repository metadata.
Is CVE-2026-66375 being exploited?
Not confirmed. CVE-2026-66375 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-66375?
CVE-2026-66375 is rated High with a CVSS score of 8.1. 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-66375?
Yes. A fix has been recorded for CVE-2026-66375. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66375 affect?
CVE-2026-66375 affects Source code repositories, Artifact/release repositories, Self-hosted DevOps platforms, Repository management applications. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66375?
Limit low‑privilege write/delete rights, audit repo metadata changes, and apply vendor patches when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated low‑privilege user can permanently remove protected internal metadata across repositories, causing data integrity loss, supply-chain risk, and possible escalation or service disruption.
Patch when possible
- affected< 7.146.35
- affected>= 7.161.0 and < 7.161.16
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.