CVE-2026-58419

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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 78% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

Notification API leaks private issue metadata after access revocation

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
21.7%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 6, 2026

Advisory Details (4)

Auto-updated Jul 6, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_release.
generic

Gitea 1.26.3 and 1.26.4 are released | Gitea Blog

https://blog.gitea.com/release-of-1.26.3-and-1.26.4/
github_release Patch Available

v1.26.4

Patch available: go-gitea/gitea v1.26.4

https://github.com/go-gitea/gitea/releases/tag/v1.26.4
github_pr

fix: Various sec fixes

Fix merged in go-gitea/gitea PR #38108 on 2026-06-17 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/38108
github Patch Available🟡 PoC Available

Notification API leaks private issue metadata after access revocation · Advisory · go-gitea/gitea · GitHub

Affected: v1.25.4 to prevent users from accessing private repository information through no

https://github.com/go-gitea/gitea/security/advisories/GHSA-44qc-pgvp-wx7v

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 46× 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-07-15 18:55 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 08:01 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 21:08 UTCEG score recompute
  8. 2026-07-14 10:14 UTCEG score recompute
  9. 2026-07-13 23:21 UTCEG score recompute
  10. 2026-07-13 22:31 UTCEPSS rescore
  11. 2026-07-13 12:28 UTCEG score recompute
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 01:34 UTCEG score recompute
  15. 2026-07-12 14:39 UTCEG score recompute
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-12 03:45 UTCEG score recompute
  18. 2026-07-11 16:52 UTCEG score recompute
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-11 05:59 UTCEG score recompute
  22. 2026-07-10 19:05 UTCEG score recompute
  23. 2026-07-10 08:11 UTCEG score recompute
  24. 2026-07-09 21:18 UTCEG score recompute
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 21 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 10:25 UTCEG score recompute
  3. 2026-07-08 23:31 UTCEG score recompute
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-08 12:38 UTCEG score recompute
  7. 2026-07-08 01:43 UTCEG score recompute
  8. 2026-07-07 14:48 UTCEG score recompute
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-07 03:56 UTCEG score recompute
  12. 2026-07-06 17:01 UTCEG score recompute▲ 7.50
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 15:36 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:31 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-03 22:30 UTCEG score recompute
  21. 2026-07-03 22:27 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58419?
CVE-2026-58419 is a high vulnerability published on July 3, 2026. Notification API leaks private issue metadata after access revocation
When was CVE-2026-58419 disclosed?
CVE-2026-58419 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58419 actively exploited?
CVE-2026-58419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58419?
CVE-2026-58419 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-58419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58419, 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

Explore the affected products and dependency analysis for CVE-2026-58419

Explore →

Is Your Infrastructure Affected by CVE-2026-58419?

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

Start Free Scan →Browse All CVEs