Private Repository Metadata Remains Accessible After Access Revocation
CVE-2026-58434
This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 14, 2026Private Repository Metadata Remains Accessible After Access Revocation · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-j2w3-9c3r-g83qVendor Advisories for CVE-2026-58434(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(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 52× 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 20:58 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 08:56 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 11:15 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 22:31 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 20:23 UTCEG score recompute
- 2026-09-05 08:29 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:14 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 02:11 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 23:09 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:43 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
Show 31 moreShow fewer
- 2026-08-25 22:35 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 21:42 UTCEG score recompute
- 2026-08-24 09:46 UTCEG score recompute
- 2026-08-23 09:58 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 10:11 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 10:14 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 22:30 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 21:48 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 19:11 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:02 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:30 UTCEG score recompute▲ 7.50
- 2026-08-14 17:30 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-08-13 17:17 UTCNVD update
- 2026-08-13 17:01 UTCMITRE cvelistV5
- 2026-08-02 00:22 UTCEG score recompute
- 2026-07-29 17:10 UTCEG score recompute
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-21 21:21 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-58434?
When was CVE-2026-58434 disclosed?
Is CVE-2026-58434 actively exploited?
What is the CVSS score of CVE-2026-58434?
How do I remediate CVE-2026-58434?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58434
Is Your Infrastructure Affected by CVE-2026-58434?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.