CVE-2025-12627

LOWPre-NVD 2.42.4—
EchelonGraph scoreHIGH confidence

Score 2.4 from GitHub Security Advisory (severity: LOW) published 2026-08-06. a secondary CVSS source baseline 2.4; sources differ by 0.0.

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

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

The user impersonation flow in WSO2 Identity Server fails to properly manage refresh tokens associated with impersonated sessions. This allows an attacker who has obtained an access token for an impersonated user to leverage the refresh token grant to obtain new access tokens, extending their ability to act as the legitimate user.

An attacker who gains access to an impersonated user's access token can exploit this weakness to renew their authorization. This results in the continued ability to perform actions on behalf of the actual user, compromising log integrity and traceability by masking the true actor.

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

Published

August 6, 2026

Last Modified

August 10, 2026

References (1)

Vendor Advisories for CVE-2025-12627(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 12× 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-08-20 06:10 UTCEG score recompute
  2. 2026-08-20 06:10 UTCGHSA enrichment
  3. 2026-08-19 17:02 UTCEPSS rescore
  4. 2026-08-18 13:47 UTCEPSS rescore
  5. 2026-08-17 13:46 UTCEPSS rescore
  6. 2026-08-17 00:57 UTCEG score recompute
  7. 2026-08-17 00:57 UTCGHSA enrichment
  8. 2026-08-16 14:55 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-16 02:13 UTCEPSS rescore
  11. 2026-08-15 01:29 UTCEPSS rescore
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-13 19:43 UTCEG score recompute
  14. 2026-08-13 19:43 UTCGHSA enrichment
  15. 2026-08-12 13:49 UTCEPSS rescore
  16. 2026-08-11 13:41 UTCEPSS rescore
  17. 2026-08-10 23:59 UTCEPSS rescore
  18. 2026-08-10 14:30 UTCGHSA enrichment
  19. 2026-08-09 21:01 UTCEG score recompute
  20. 2026-08-09 21:01 UTCGHSA enrichment
  21. 2026-08-09 13:45 UTCEPSS rescore
  22. 2026-08-07 16:26 UTCEPSS rescore
  23. 2026-08-06 15:48 UTCEG score recompute
  24. 2026-08-06 15:48 UTCGHSA enrichment
  25. 2026-08-06 13:45 UTCEPSS rescore
Show 7 more
  1. 2026-08-06 13:36 UTCEG score recompute
  2. 2026-08-06 13:36 UTCGHSA enrichment
  3. 2026-08-06 13:09 UTCEG score recompute
  4. 2026-08-06 13:09 UTCGHSA enrichment
  5. 2026-08-06 08:21 UTCEG score recompute
  6. 2026-08-06 08:09 UTCEG score recompute
  7. 2026-08-06 08:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-12627?
CVE-2025-12627 is a low vulnerability published on August 6, 2026. The user impersonation flow in WSO2 Identity Server fails to properly manage refresh tokens associated with impersonated sessions. This allows an attacker who has obtained an access token for an impersonated user to leverage the refresh token grant to obtain new access tokens, extending their…
When was CVE-2025-12627 disclosed?
CVE-2025-12627 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-12627 actively exploited?
CVE-2025-12627 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 96.9% of all scored CVEs.
What is the CVSS score of CVE-2025-12627?
CVE-2025-12627 has a CVSS v3 base score of 2.4 (NVD).
How do I remediate CVE-2025-12627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-12627, 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-12627

Explore →

Is Your Infrastructure Affected by CVE-2025-12627?

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

Start Free Scan →Browse All CVEs