CVE-2025-22149
LOWDescription
JWK Set (JSON Web Key Set) is a JWK and JWK Set Go implementation. Prior to 0.6.0, the project's provided HTTP client's local JWK Set cache should do a full replacement when the goroutine refreshes the remote JWK Set. The current behavior is to overwrite or append. This is a security issue for use cases that utilize the provided auto-caching HTTP client and where key removal from a JWK Set is equivalent to revocation. The affected auto-caching HTTP client was added in version v0.5.0 and fixed in v0.6.0. The only workaround would be to remove the provided auto-caching HTTP client and replace it with a custom implementation. This involves setting the HTTPClientStorageOptions.RefreshInterval to zero (or not specifying the value).
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Moderate risk: more likely to be exploited than 45% of all known CVEs.
References
Related Vulnerabilities
Other CWE-672 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-23638 | Medium | 6.5 | 60% | - | Fix |
| CVE-2020-11027 | Medium | 6.1 | 14% | - | Fix |
| CVE-2019-17638 | Critical | 9.4 | 11% | - | Fix |
| CVE-2009-3547 | High | 7.0 | 4.9% | - | - |
| CVE-2019-15691 | High | 7.2 | 4.7% | - | Fix |
| CVE-2020-24030 | Critical | 9.8 | 2.7% | - | - |
Common questions
How do I fix CVE-2025-22149?
No published fix for CVE-2025-22149 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2025-22149 being actively exploited?
Not that we know of. CVE-2025-22149 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.56% is the estimated probability that it will be exploited in the next 30 days. That is higher than 45% of all scored CVEs.
How severe is CVE-2025-22149?
CVE-2025-22149 has a CVSS v4 base score of 2.1, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2025-22149
Markdown
[](https://tridentstack.com/cve/CVE-2025-22149)HTML
<a href="https://tridentstack.com/cve/CVE-2025-22149"><img src="https://tridentstack.com/cve/badge/CVE-2025-22149.svg" alt="CVE-2025-22149"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.