Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

duende.accesstokenmanagement

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.3NuGetPublished

    Duende.AccessTokenManagement race condition when concurrently retrieving customized Client Credentials Access Tokens

    CVE-2025-26620 · GHSA-qxj7-2x7w-3mpp

    Affected
    • NuGet duende.accesstokenmanagement < 3.2.0
    Fixed in
    3.2.0· Vendor fix available
    Issue
    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. Details 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() - IClientCredentialsTokenManagementService.GetAccessTokenAsync() There are overloads of both of these methods that accept a TokenRequestParameters object that customizes token request parameters.…

    Recommended action: Upgrade to 3.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →