Is Duende.AccessTokenManagement 3.0 vulnerable?

NuGet · 1 release from 3.0.1 to 3.0.1 · latest Duende.AccessTokenManagement is 4.3.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. Duende.AccessTokenManagement 3.0.1, the last 3.0 release, is affected by 1 known security advisory (1 medium), including CVE-2025-26620. Upgrade to 3.2.0 or later to fix all of them.

Upgrade with:dotnet add package Duende.AccessTokenManagement --version 3.2.0

Is your project on an affected Duende.AccessTokenManagement?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting Duende.AccessTokenManagement 3.0.1

  • MediumCVE-2025-26620GHSA-qxj7-2x7w-3mpp19 Feb 2025

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

    Affected
    <3.2.0
    Fixed in
    3.2.0

Which of your client projects are still on Duende.AccessTokenManagement 3.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Duende.AccessTokenManagement version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other Duende.AccessTokenManagement versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.