CVE-2026-57894
Repository migration follows HTTP redirects, allowing internal Git repo exfiltration.
Is CVE-2026-57894 being exploited?
Not confirmed. CVE-2026-57894 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-57894?
CVE-2026-57894 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-57894?
Yes. A fix has been recorded for CVE-2026-57894. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57894 affect?
CVE-2026-57894 affects Git hosting platforms with repository migration/import features, Self-hosted Git servers and enterprise Git appliances, CI/CD systems that perform automated repository imports. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57894?
Disable migration/import, block outbound redirects, restrict migration targets, apply vendor patch when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can trick migration to follow redirects after URL allow/block checks to access and exfiltrate internal Git repositories and secrets.
Immediate action required
- affected<= 1.26.4
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.