Revoked-key acceptance via additive cache refresh
Published Jan 9, 2025 · Updated May 23, 2025
Improper cache refresh in Micah Parks jwkset 0.5.0 through 0.5.21 allows attackers to keep revoked keys usable via its HTTP client. The refresh goroutine decodes the current remote JWK Set and writes each key into the existing MemoryJWKSet without first deleting keys absent from the response. Exploitation requires the auto-caching HTTP client with a nonzero refresh interval, a stolen private key, upstream removal of that key, and no other revocation control; forged content can then remain accepted.
Summary
What happened
Improper cache refresh in Micah Parks jwkset 0.5.0 through 0.5.21 allows attackers to keep revoked keys usable via its HTTP client. The refresh goroutine decodes the current remote JWK Set and writes each key into the existing MemoryJWKSet without first deleting keys absent from the response. Exploitation requires the auto-caching HTTP client with a nonzero refresh interval, a stolen private key, upstream removal of that key, and no other revocation control; forged content can then remain accepted.
The record
- CVE
- CVE-2025-22149
- Published
- Jan 9, 2025
- Updated
- May 23, 2025
- Vendor
- Micah Parks
- Product
- jwkset
- Classifications
- CWE-672
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 9, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.5.0, < 0.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo