CVE-2026-58510

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Elevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
35(Track)
EG Risk 35/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 computed
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 21, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-q423-49rw-g9mh

Vendor Advisories for CVE-2026-58510(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)
PackageVulnerable rangeFixed inDependents
code.gitea.io/gitea—1.27.0—
gitea.dev—1.27.0—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 42× 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.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-14 03:10 UTCEG score recompute
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-13 02:02 UTCEG score recompute
  5. 2026-09-12 00:53 UTCEG score recompute
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-10 22:08 UTCEG score recompute
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-07 21:44 UTCEG score recompute
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-05 19:36 UTCEG score recompute
  13. 2026-09-04 14:19 UTCEG score recompute
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 23:43 UTCEG score recompute
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-31 02:09 UTCEG score recompute
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-30 01:01 UTCEG score recompute
  23. 2026-08-28 21:42 UTCEPSS rescore
  24. 2026-08-27 21:10 UTCEG score recompute
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 32 more
  1. 2026-08-26 17:43 UTCEG score recompute
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-26 11:39 UTCEG score recompute
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-25 10:31 UTCEG score recompute
  6. 2026-08-23 08:13 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 07:05 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 05:56 UTCEG score recompute
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 04:47 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 03:38 UTCEG score recompute
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 01:28 UTCEG score recompute
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 23:48 UTCEG score recompute
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 22:40 UTCEG score recompute
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 20:23 UTCEG score recompute
  24. 2026-08-13 19:23 UTCEG score recompute▲ 4.30
  25. 2026-08-13 19:21 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
  26. 2026-08-13 17:17 UTCNVD update
  27. 2026-08-13 17:04 UTCEG score recompute▼ 4.30
  28. 2026-08-13 17:01 UTCMITRE cvelistV5
  29. 2026-07-30 14:41 UTCEG score recompute
  30. 2026-07-27 11:02 UTCEG score recompute
  31. 2026-07-23 03:21 UTCEG score recompute
  32. 2026-07-21 22:19 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58510?
CVE-2026-58510 is a medium vulnerability published on July 21, 2026. GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private
When was CVE-2026-58510 disclosed?
CVE-2026-58510 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58510 actively exploited?
CVE-2026-58510 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.8% of all scored CVEs.
What is the CVSS score of CVE-2026-58510?
CVE-2026-58510 has a CVSS v3.1 base score of 4.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-58510?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58510, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58510

Explore →

Is Your Infrastructure Affected by CVE-2026-58510?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs