CVE-2026-24791

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 84% 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
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: Elevated riskExposed: 0

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

Public-only tokens bypass private-resource restrictions on /api/v1/user self routes

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

June 17, 2026

Last Modified

August 26, 2026

Advisory Details (4)

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

Gitea 1.26.2 is released | Gitea Blog

https://blog.gitea.com/release-of-1.26.2/
github_release Patch Available

v1.26.2

Patch available: go-gitea/gitea v1.26.2

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

fix: Unify public-only token filtering in API queries and repo access checks

Fix merged in go-gitea/gitea PR #37118 on 2026-05-18 — awaiting tagged release

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

Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routes · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-wrr5-99h5-gq57

Vendor Advisories for CVE-2026-24791(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
code.gitea.io/gitea1.26.2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× 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-16 05:15 UTCEPSS rescore
  2. 2026-09-14 03:07 UTCEG score recompute
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-13 14:13 UTCEG score recompute
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 21:19 UTCEG score recompute
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 17:44 UTCEG score recompute
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-24 22:24 UTCEG score recompute
  24. 2026-08-23 04:14 UTCEG score recompute
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 24 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 09:30 UTCEG score recompute
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 08:13 UTCEG score recompute
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-19 08:10 UTCEG score recompute
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 22:05 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 09:48 UTCEG score recompute
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 09:12 UTCEG score recompute
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 07:38 UTCEG score recompute
  16. 2026-08-13 18:52 UTCEG score recompute 8.10
  17. 2026-08-13 18:51 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  18. 2026-08-13 17:17 UTCNVD update
  19. 2026-08-13 17:05 UTCEG score recompute 8.10
  20. 2026-08-13 17:01 UTCMITRE cvelistV5
  21. 2026-07-30 22:37 UTCEG score recompute
  22. 2026-07-26 19:05 UTCEG score recompute
  23. 2026-07-23 03:07 UTCEG score recompute
  24. 2026-06-17 18:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-24791?
CVE-2026-24791 is a high vulnerability published on June 17, 2026. Public-only tokens bypass private-resource restrictions on /api/v1/user self routes
When was CVE-2026-24791 disclosed?
CVE-2026-24791 was first published in the National Vulnerability Database on June 17, 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-24791 actively exploited?
CVE-2026-24791 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 83.4% of all scored CVEs.
What is the CVSS score of CVE-2026-24791?
CVE-2026-24791 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-24791?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24791, 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-24791

Explore →

Is Your Infrastructure Affected by CVE-2026-24791?

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