CVE-2025-26620

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.3 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-4683 (ENISA EUVD) · GHSA-qxj7-2x7w-3mpp (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Duende.AccessTokenManagement is a set of .NET libraries that manage OAuth and OpenId Connect access tokens. Duende.AccessTokenManagement contains a race condition when requesting access tokens using the client credentials flow. Concurrent requests to obtain an access token using differing protocol parameters can return access tokens obtained with the wrong scope, resource indicator, or other protocol parameters. Such usage is somewhat atypical, and only a small percentage of users are likely to be affected. Duende.AccessTokenManagement can request access tokens using the client credentials flow in several ways. In basic usage, the client credentials flow is configured once and the parameters do not vary. In more advanced situations, requests with varying protocol parameters may be made by calling specific overloads of these methods: HttpContext.GetClientAccessTokenAsync() and IClientCredentialsTokenManagementService.GetAccessTokenAsync(). There are overloads of both of these methods that accept a TokenRequestParameters object that customizes token request parameters. However, concurrent requests with varying TokenRequestParameters will result in the same token for all concurrent calls. Most users can simply update the NuGet package to the latest version. Customizations of the IClientCredentialsTokenCache that derive from the default implementation (DistributedClientCredentialsTokenCache) will require a small code change, as its constructor was changed to add a dependency on the ITokenRequestSynchronization service. The synchronization service will need to be injected into the derived class and passed to the base constructor. The impact of this vulnerability depends on how Duende.AccessTokenManagement is used and on the security architecture of the solution. Most users will not be vulnerable to this issue. More advanced users may run into this issue by calling the methods specified above with customized token request parameters. The impact of obtaining an access token with different than intended protocol parameters will vary depending on application logic, security architecture, and the authorization policy of the resource servers.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 18, 2025

Last Modified

April 15, 2026

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
nugetDuende.AccessTokenManagement @ 3.2.0 (fixes < 3.2.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
Duende.AccessTokenManagement1.0.0 ... 3.1.1 (13 versions)
  • every version up to 3.2.0: fixed in 3.2.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 227 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 131 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-01 08:08 UTCEG score recompute
  4. 2026-11-01 08:08 UTCGHSA enrichmentGHSA-qxj7-2x7w-3mpp · GitHub severity MODERATE
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-25 16:39 UTCEG score recompute
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-24 00:41 UTCEG score recompute
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-18 05:42 UTCEG score recompute
  22. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 71 more
  1. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-12 17:15 UTCEG score recompute
  3. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-11 20:47 UTCEG score recompute
  5. 2026-10-11 18:57 UTCEG score recompute
  6. 2026-10-11 15:35 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-10 22:17 UTCOSV refresh
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-02 16:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-09-21 10:19 UTCOSV refresh
  27. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  30. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  31. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  32. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  33. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  40. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  41. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  42. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  43. 2026-09-02 08:44 UTCOSV refresh
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  48. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  52. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  53. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  54. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  55. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  56. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  57. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  58. 2026-08-16 07:54 UTCOSV refresh
  59. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  60. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  62. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  64. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  65. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  67. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  68. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  69. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  70. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  71. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-26620?
CVE-2025-26620 is a medium-severity vulnerability; its CVE record was published on February 18, 2025. Duende.AccessTokenManagement is a set of .NET libraries that manage OAuth and OpenId Connect access tokens. Duende.AccessTokenManagement contains a race condition when requesting access tokens using the client credentials flow. Concurrent requests to obtain an access token using differing protocol…
When was the CVE record for CVE-2025-26620 published?
The CVE record for CVE-2025-26620 was published on February 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-26620 actively exploited?
CVE-2025-26620 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-26620?
CVE-2025-26620 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2025-26620?
A fix for CVE-2025-26620 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-26620

Explore →

Is Your Infrastructure Affected by CVE-2025-26620?

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

Book a Demo →Browse All CVEs