CVE-2025-12317

MEDIUMPre-NVD 5.05.0
EchelonGraph scoreHIGH confidence

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

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

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

When internal roles are removed from a user within the WSO2 product, the system fails to invalidate any previously issued authentication tokens associated with that user.

This vulnerability could allow users to retain their previous access privileges even after their roles have been revoked. As a result, a user can continue to perform unauthorized actions or access restricted resources until the expired tokens naturally expire.

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

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2025-12317(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 21× in last 7d / 41× 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 03:46 UTCEG score recompute
  2. 2026-08-20 03:46 UTCGHSA enrichment
  3. 2026-08-19 17:02 UTCEPSS rescore
  4. 2026-08-19 02:59 UTCEG score recompute
  5. 2026-08-19 02:59 UTCGHSA enrichment
  6. 2026-08-18 13:47 UTCEPSS rescore
  7. 2026-08-18 01:50 UTCEG score recompute
  8. 2026-08-18 01:50 UTCGHSA enrichment
  9. 2026-08-17 13:46 UTCEPSS rescore
  10. 2026-08-17 01:05 UTCEG score recompute
  11. 2026-08-17 01:05 UTCGHSA enrichment
  12. 2026-08-16 14:55 UTCEPSS rescore
  13. 2026-08-16 02:13 UTCEPSS rescore
  14. 2026-08-16 02:13 UTCEPSS rescore
  15. 2026-08-16 00:21 UTCEG score recompute
  16. 2026-08-16 00:21 UTCGHSA enrichment
  17. 2026-08-15 01:29 UTCEPSS rescore
  18. 2026-08-14 23:37 UTCGHSA enrichment
  19. 2026-08-13 22:52 UTCEG score recompute
  20. 2026-08-13 22:52 UTCGHSA enrichment
  21. 2026-08-13 21:59 UTCEPSS rescore
  22. 2026-08-12 22:08 UTCEG score recompute
  23. 2026-08-12 22:08 UTCGHSA enrichment
  24. 2026-08-12 13:49 UTCEPSS rescore
  25. 2026-08-11 21:24 UTCEG score recompute
Show 16 more
  1. 2026-08-11 21:24 UTCGHSA enrichment
  2. 2026-08-11 13:41 UTCEPSS rescore
  3. 2026-08-10 23:59 UTCEPSS rescore
  4. 2026-08-10 20:40 UTCGHSA enrichment
  5. 2026-08-09 19:56 UTCEG score recompute
  6. 2026-08-09 19:56 UTCGHSA enrichment
  7. 2026-08-09 13:45 UTCEPSS rescore
  8. 2026-08-08 19:12 UTCEG score recompute
  9. 2026-08-08 19:12 UTCGHSA enrichment
  10. 2026-08-07 18:27 UTCEG score recompute
  11. 2026-08-07 18:27 UTCGHSA enrichment
  12. 2026-08-07 18:08 UTCEG score recompute
  13. 2026-08-07 18:08 UTCGHSA enrichment
  14. 2026-08-07 16:26 UTCEPSS rescore
  15. 2026-08-06 22:16 UTCEG score recompute
  16. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-12317?
CVE-2025-12317 is a medium vulnerability published on August 6, 2026. When internal roles are removed from a user within the WSO2 product, the system fails to invalidate any previously issued authentication tokens associated with that user. This vulnerability could allow users to retain their previous access privileges even after their roles have been revoked. As a…
When was CVE-2025-12317 disclosed?
CVE-2025-12317 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-12317 actively exploited?
CVE-2025-12317 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 84.6% of all scored CVEs.
What is the CVSS score of CVE-2025-12317?
CVE-2025-12317 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2025-12317?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-12317, 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-2025-12317

Explore →

Is Your Infrastructure Affected by CVE-2025-12317?

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