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.
Metrics
Affected Vendors & Products
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sat, 27 Sep 2025 00:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | |
Title | get-jwks poisoned JWKS cache allows post-fetch issuer validation bypass | |
Weaknesses | CWE-116 | |
References |
| |
Metrics |
cvssV3_0
|

Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-09-27T00:22:10.412Z
Reserved: 2025-09-23T14:33:49.505Z
Link: CVE-2025-59936

No data.

Status : Received
Published: 2025-09-27T01:15:43.590
Modified: 2025-09-27T01:15:43.590
Link: CVE-2025-59936

No data.

No data.