Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository Exfiltration
CVE-2026-57894
This high-severity CVE scores 8.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(medium)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity85% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 14, 2026Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository Exfiltration · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-82f7-87hm-852xVendor Advisories for CVE-2026-57894(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| code.gitea.io/gitea | — | 1.27.0 | — |
| gitea.dev | — | 1.27.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 51× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:01 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 11:19 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 22:34 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 20:12 UTCEG score recompute
- 2026-09-05 08:32 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 00:56 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 03:00 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 02:13 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 22:57 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:44 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 18:41 UTCEG score recompute
Show 30 moreShow fewer
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 19:19 UTCEG score recompute
- 2026-08-23 08:16 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 08:55 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 09:35 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 22:34 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:59 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 20:52 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 18:15 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:34 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 07:15 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:39 UTCEG score recompute
- 2026-08-14 17:49 UTCEG score recompute▲ 8.50
- 2026-08-14 17:48 UTCMITRE cvelistV5CVSS v3 → 8.5 · severity → HIGH
- 2026-08-13 17:17 UTCNVD update
- 2026-08-13 17:05 UTCEG score recompute▼ 8.50
- 2026-08-13 17:01 UTCMITRE cvelistV5
- 2026-07-30 21:19 UTCEG score recompute
- 2026-07-26 21:42 UTCEG score recompute
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-21 19:19 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-57894?
When was CVE-2026-57894 disclosed?
Is CVE-2026-57894 actively exploited?
What is the CVSS score of CVE-2026-57894?
How do I remediate CVE-2026-57894?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57894
Is Your Infrastructure Affected by CVE-2026-57894?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.