How severe is GHSA-7mr7-4f54-vcx5?

GHSA-7mr7-4f54-vcx5 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 GHSA-7mr7-4f54-vcx5?

GHSA-7mr7-4f54-vcx5 affects the following packages: Duende.AccessTokenManagement.OpenIdConnect (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-7mr7-4f54-vcx5?

Update Duende.AccessTokenManagement.OpenIdConnect to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mr7-4f54-vcx5 is resolved across your whole dependency graph.

How do I detect GHSA-7mr7-4f54-vcx5 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 GHSA-7mr7-4f54-vcx5 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 GHSA-7mr7-4f54-vcx5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7mr7-4f54-vcx5 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 GHSA-7mr7-4f54-vcx5?

GHSA-7mr7-4f54-vcx5 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 GHSA-7mr7-4f54-vcx5?

GHSA-7mr7-4f54-vcx5 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 GHSA-7mr7-4f54-vcx5 published, and has it been updated?

GHSA-7mr7-4f54-vcx5 was published on November 7, 2024 and was last updated on November 8, 2024. 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

HTTP Client uses incorrect token after refreshGHSA-7mr7-4f54-vcx5

MEDIUMFix: DuendeSoftware/Duende.AccessTokenManagement@09c73e3

GHSA-7mr7-4f54-vcx5 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.

Also known asCVE-2024-51987

Published

Nov 7, 2024

Updated

Nov 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 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 GHSA-7mr7-4f54-vcx5.

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 GHSA-7mr7-4f54-vcx5 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

### Impact HTTP Clients created by `AddUserAccessTokenHttpClient` may use a different user's access token after a token refresh. This occurs because a refreshed token will be captured in pooled `HttpClient` instances, which may be used by a different user. ### Workarounds 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. ### Patches This issue is fixed in Duende.AccessTokenM