Vulnerability · Published Sep 27, 2025 · Assigned by GitHub_M

CVE-2025-59936get-jwks poisoned JWKS cache allows post-fetch issuer validation bypass

Critical 9.4

In plain English

A critical-severity security flaw in get-jwks from nearform. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 35% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.0)9.4Critical
Exploit odds (30 days)0.4%top 65.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

get-jwks contains fetch utils for JWKS keys. In versions prior to 11.0.2, a vulnerability in get-jwks can lead to cache poisoning in the JWKS key-fetching mechanism. When the iss (issuer) claim is validated only after keys are retrieved from the cache, it is possible for cached keys from an unexpected issuer to be reused, resulting in a bypass of issuer validation. This design flaw enables a potential attack where a malicious actor crafts a pair of JWTs, the first one ensuring that a chosen public key is fetched and stored in the shared JWKS cache, and the second one leveraging that cached key to pass signature validation for a targeted iss value. The vulnerability will work only if the iss validation is done after the use of get-jwks for keys retrieval. This issue has been patched in version 11.0.2.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmget-jwks11.0.2GHSA-qc2q-qhf3-235m

Affected products (as reported)

VendorProductVersions
nearform get-jwks < 11.0.2

Weakness: CWE-116 · Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

References