CVE-2026-24059

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-08-13. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

The GET /api/v1/user/actions/runners/registration-token endpoint (and its owner- and repository-level equivalents) creates a new runner registration token if none exists, yet the API scope middleware classifies it as read-only because it is a GET request. A holder of a leaked read:user-scoped token can therefore mint a registration token and register a malicious Actions runner that executes workflow jobs with access to repository secrets and source code.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (3)

Auto-updated Aug 14, 2026
Patch available. Sources: github_pr, github_release.
generic

Gitea 1.25.5 is released | Gitea Blog

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

v1.25.5

Patch available: go-gitea/gitea v1.25.5

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

Remove API registration-token

Fix merged in go-gitea/gitea PR #36801 on 2026-03-02 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/36801

Vendor Advisories for CVE-2026-24059(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 29× 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-08-21 02:11 UTCEG score recompute
  2. 2026-08-21 02:11 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 04:32 UTCEG score recompute
  5. 2026-08-20 04:32 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 06:52 UTCEG score recompute
  8. 2026-08-19 06:52 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 09:14 UTCEG score recompute
  11. 2026-08-18 09:13 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 11:32 UTCEG score recompute
  14. 2026-08-17 11:32 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 13:53 UTCEG score recompute
  17. 2026-08-16 13:53 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 16:14 UTCEG score recompute
  20. 2026-08-15 16:14 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 18:35 UTCEG score recompute
  23. 2026-08-14 18:35 UTCGHSA enrichment
  24. 2026-08-14 17:30 UTCEG score recompute▲ 6.50
  25. 2026-08-14 17:30 UTCGHSA enrichment
Show 4 more
  1. 2026-08-14 17:30 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  2. 2026-08-13 17:17 UTCNVD update
  3. 2026-08-13 17:02 UTCEG score recompute
  4. 2026-08-13 17:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24059?
CVE-2026-24059 is a medium vulnerability published on August 13, 2026. The GET /api/v1/user/actions/runners/registration-token endpoint (and its owner- and repository-level equivalents) creates a new runner registration token if none exists, yet the API scope middleware classifies it as read-only because it is a GET request. A holder of a leaked read:user-scoped token…
When was CVE-2026-24059 disclosed?
CVE-2026-24059 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24059 actively exploited?
CVE-2026-24059 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 76.8% of all scored CVEs.
What is the CVSS score of CVE-2026-24059?
CVE-2026-24059 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-24059?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24059, 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-24059

Explore →

Is Your Infrastructure Affected by CVE-2026-24059?

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

Start Free Scan →Browse All CVEs