CVE-2026-24451

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.5%, top 62% 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.

Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.

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

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (4)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github.
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.3

Patch available: go-gitea/gitea v1.26.3

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

fix: Various security fixes (#38103)

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

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

Fork Synchronization Continues After Parent Repository Changes from Public to Private · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-wrf9-r3h7-7x5v

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24451?
CVE-2026-24451 is a high vulnerability published on July 3, 2026. Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.
When was CVE-2026-24451 disclosed?
CVE-2026-24451 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24451 actively exploited?
CVE-2026-24451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-24451?
CVE-2026-24451 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-24451?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24451, 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-24451

Explore →

Is Your Infrastructure Affected by CVE-2026-24451?

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

Start Free Scan →Browse All CVEs