Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-7mr7-4f54-vcx5

HTTP Client uses incorrect token after refresh

CVSS 5.4 MediumEPSS 0.0024 · 15th percentile

Published by the GitHub Advisory Database at 7 Nov 2024, 21:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
Duende.AccessTokenManagement.OpenIdConnectNuGet>=3.0.0, <3.0.13.0.1
Identifiers
GHSA-7mr7-4f54-vcx5 · CVE-2024-51987
Weakness (CWE)
CWE-270
Tags
Published
7 Nov 2024
Updated
8 Nov 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

HTTP clients created by Duende.AccessTokenManagement.OpenIdConnect versions >=3.0.0 and <3.0.1 can send a different user's access token after a token refresh, because refreshed tokens are captured in pooled HttpClient instances. The source does not describe what an attacker must do to trigger this. Upgrade to version 3.0.1; as a workaround, call HttpContext.GetUserAccessTokenAsync or IUserTokenManagementService.GetAccessTokenAsync directly instead of using AddUserAccessTokenHttpClient.

Written 9 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0024, the 15th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:23 UTC First seen by agentprime
  2. 31 Oct 2026, 15:23 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.