CVE-2024-8995

MEDIUMPre-NVD 4.94.9
EchelonGraph scoreHIGH confidence

Score 4.9 from GitHub Security Advisory published 2026-08-06. a secondary CVSS source baseline 4.9; sources differ by 0.0.

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

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

Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused.

If an attacker possesses both the authorization code and the associated client credentials (client ID and client secret), they can leverage these unused codes to obtain access tokens on behalf of users who have already been deleted. This may lead to unauthorized access to sensitive resources and services, contingent on the scopes originally authorized for the compromised authorization code.

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

Published

August 6, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2024-8995(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 18× in last 7d / 44× 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-20 22:54 UTCEPSS rescore
  2. 2026-08-20 22:27 UTCGHSA enrichment
  3. 2026-08-19 21:27 UTCEG score recompute
  4. 2026-08-19 21:27 UTCGHSA enrichment
  5. 2026-08-19 17:02 UTCEPSS rescore
  6. 2026-08-18 20:25 UTCEG score recompute
  7. 2026-08-18 20:25 UTCGHSA enrichment
  8. 2026-08-18 13:47 UTCEPSS rescore
  9. 2026-08-17 19:26 UTCGHSA enrichment
  10. 2026-08-16 16:40 UTCEG score recompute
  11. 2026-08-16 16:40 UTCGHSA enrichment
  12. 2026-08-16 14:55 UTCEPSS rescore
  13. 2026-08-16 02:13 UTCEPSS rescore
  14. 2026-08-15 15:36 UTCEG score recompute
  15. 2026-08-15 15:36 UTCGHSA enrichment
  16. 2026-08-15 01:29 UTCEPSS rescore
  17. 2026-08-14 14:36 UTCEG score recompute
  18. 2026-08-14 14:36 UTCGHSA enrichment
  19. 2026-08-13 21:59 UTCEPSS rescore
  20. 2026-08-13 13:36 UTCGHSA enrichment
  21. 2026-08-12 21:10 UTCEG score recompute
  22. 2026-08-12 21:10 UTCGHSA enrichment
  23. 2026-08-12 13:49 UTCEPSS rescore
  24. 2026-08-11 20:09 UTCEG score recompute
  25. 2026-08-11 20:09 UTCGHSA enrichment
Show 19 more
  1. 2026-08-10 23:58 UTCEPSS rescore
  2. 2026-08-10 19:10 UTCGHSA enrichment
  3. 2026-08-09 18:47 UTCGHSA enrichment
  4. 2026-08-08 17:48 UTCEG score recompute
  5. 2026-08-08 17:48 UTCGHSA enrichment
  6. 2026-08-08 16:35 UTCEPSS rescore
  7. 2026-08-07 16:48 UTCEG score recompute
  8. 2026-08-07 16:48 UTCGHSA enrichment
  9. 2026-08-07 16:26 UTCEPSS rescore
  10. 2026-08-06 15:48 UTCEG score recompute
  11. 2026-08-06 15:48 UTCGHSA enrichment
  12. 2026-08-06 13:45 UTCEPSS rescore
  13. 2026-08-06 13:36 UTCEG score recompute
  14. 2026-08-06 13:36 UTCGHSA enrichment
  15. 2026-08-06 13:09 UTCEG score recompute
  16. 2026-08-06 13:09 UTCGHSA enrichment
  17. 2026-08-06 08:21 UTCEG score recompute
  18. 2026-08-06 08:09 UTCEG score recompute
  19. 2026-08-06 08:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2024-8995?
CVE-2024-8995 is a medium vulnerability published on August 6, 2026. Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused. If an attacker possesses both the authorization code and the associated client credentials…
When was CVE-2024-8995 disclosed?
CVE-2024-8995 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-8995 actively exploited?
CVE-2024-8995 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 97.9% of all scored CVEs.
What is the CVSS score of CVE-2024-8995?
CVE-2024-8995 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2024-8995?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-8995, 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-2024-8995

Explore →

Is Your Infrastructure Affected by CVE-2024-8995?

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