How severe is CVE-2024-51987?

CVE-2024-51987 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-51987?

CVE-2024-51987 affects the following packages: Duende.AccessTokenManagement.OpenIdConnect (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2024-51987?

Update Duende.AccessTokenManagement.OpenIdConnect to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-51987 is resolved across your whole dependency graph.

How do I detect CVE-2024-51987 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Duende.AccessTokenManagement.OpenIdConnect, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-51987 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-51987 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-51987 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-51987?

CVE-2024-51987 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 15th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-51987?

CVE-2024-51987 is classified as CWE-270 (CWE-270). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-51987 published, and has it been updated?

CVE-2024-51987 was published on November 7, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

MEDIUM severity

CVE-2024-51987 — Duende.AccessTokenManagem…

MEDIUMFix: DuendeSoftware/Duende.AccessTokenManagement@09c73e3

CVE-2024-51987 is a medium-severity (CVSS 5.4) CWE-270 vulnerability in Duende.AccessTokenManagement.OpenIdConnect. A fix is available for Duende.AccessTokenManagement.OpenIdConnect — see the affected versions and patch details below.

HTTP Client uses incorrect token after refresh in Duende.AccessTokenManagement.OpenIdConnect

Also known asGHSA-7mr7-4f54-vcx5

Published

Nov 7, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-51987.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs15th percentile — riskier than 15% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

.NETDuende.AccessTokenManagement.OpenIdConnect

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Duende.AccessTokenManagement.OpenIdConnect is a set of .NET libraries that manage OAuth and OpenId Connect access tokens. HTTP Clients created by AddUserAccessTokenHttpClient may use a different user's access token after a token refresh occurs. This occurs because a refreshed token will be captured in pooled HttpClient instances, which may be used by a different user. Instead of using AddUserAccessTokenHttpClient to create an HttpClient that automatically adds a managed token to outgoing requests, you can use the HttpConext.GetUserAccessTokenAsync extension method or the IUserTokenManagementService.GetAccessTokenAsync method. This issue is fixed in Duende.AccessTokenManagement.OpenIdConnect 3.0.1. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Duende.AccessTokenManagement.OpenIdConnect`	≥ 3.0.0&&< 3.0.1	3.0.1`dotnet add package Duende.AccessTokenManagement.OpenIdConnect --version 3.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Duende.AccessTokenManagement.OpenIdConnect, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Duende.AccessTokenManagement.OpenIdConnect to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-51987 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Duende.AccessTokenManagement.OpenIdConnect is a set of .NET libraries that manage OAuth and OpenId Connect access tokens. HTTP Clients created by `AddUserAccessTokenHttpClient` may use a different user's access token after a token refresh occurs. This occurs because a refreshed token will be captured in pooled `HttpClient` instances, which may be used by a different user. Instead of using `AddUserAccessTokenHttpClient` to create an `HttpClient` that automatically adds a managed token to outgoing requests, you can use the `HttpConext.GetUserAccessTokenAsync` extension method or the `IUserTokenM

O3 Security · Impact-Aware SCA

Is CVE-2024-51987 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

CWE Classification

CWE-270CWE-270

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Nov 7, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2024-51987

GHSA-7mr7-4f54-vcx5

References

Advisorygithub.com · CVE 2024 51987.json Advisorygithub.com · GHSA 7mr7 4f54 vcx5 Advisorynvd.nist.gov · CVE 2024 51987 Webgithub.com · 09c73e32b182da5c6d7b55ec790cb2271cc4b63f Webgithub.com · 3.0.1 Packagegithub.com · Duende.AccessTokenManagement

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs with CWE-270 are rated as high or higher (top: critical).

CVE-2025-49583CVE-2024-47173CVE-2024-37294CVE-2023-37912CVE-2023-25754CVE-2023-26475CVE-2020-1719CVE-2020-7020Browse all CWE-270

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026