{"answers":{"affected":"3 open source packages ship an affected version, including github.com/MicahParks/jwkset.","exploited":"There is no known exploitation of CVE-2025-22149 in the wild and no public exploit code.","fix":"Upgrade github.com/MicahParks/jwkset to 0.6.0 or later.","what":"CVE-2025-22149 is a low-severity vulnerability in MicahParks jwkset, published on 9 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-22149 and fix it if it is affected.\n\nWhat it is: CVE-2025-22149 is a low-severity vulnerability in MicahParks jwkset, published on 9 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-22149 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/MicahParks/jwkset (Go): affected from 0.5.0; fixed in 0.6.0\n- github.com/MicahParks/jwkset (Go): affected from 0.5.0; fixed in 0.6.0\n- github.com/MicahParks/jwkset (Go): affected from 0.5.0; fixed in 0.6.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-22149/ (Markdown: https://insights.sbomify.com/CVE-2025-22149/index.md)","id":"CVE-2025-22149","markdown":"https://insights.sbomify.com/CVE-2025-22149/index.md","name":"CVE-2025-22149","record":{"aliases":["GHSA-675f-rq2r-jw82","GO-2025-3376"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Go JWK Set library","requires_auth":"high_privilege","summary":"Attackers can bypass key revocation in the JWK Set Go library's auto-caching client because stale keys are not removed from the local cache.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-672","name":"Operation on a Resource after Expiration or Release"}],"description":"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).","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"JWK Set's HTTP client only overwrites and appends JWK to local cache during refresh","id":"CVE-2025-22149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Undici Uses Insufficiently Random Values","id":"CVE-2025-22150"},"packages":[{"ecosystem":"Go","fixed":["0.6.0"],"introduced":["0.5.0"],"last_affected":[],"package":"github.com/MicahParks/jwkset","purl":null,"source":"GHSA-675f-rq2r-jw82"},{"ecosystem":"Go","fixed":["0.6.0"],"introduced":["0.5.0"],"last_affected":[],"package":"github.com/MicahParks/jwkset","purl":"pkg:golang/github.com/MicahParks/jwkset","source":"GHSA-675f-rq2r-jw82"},{"ecosystem":"Go","fixed":["0.6.0"],"introduced":["0.5.0"],"last_affected":[],"package":"github.com/MicahParks/jwkset","purl":"pkg:golang/github.com/MicahParks/jwkset","source":"GO-2025-3376"}],"prev":{"headline":"Improper authentication on SAML SSO process allows user impersonation in sentry","id":"CVE-2025-22146"},"products":["jwkset"],"published":"2025-01-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-23","vendors":["MicahParks"]},"summary":"Attackers can bypass key revocation in the JWK Set Go library's auto-caching client because stale keys are not removed from the local cache.","url":"https://insights.sbomify.com/CVE-2025-22149/"}