{"vulnerability": "CVE-2025-22149", "sightings": [{"uuid": "5f6d1379-8a2f-4fa7-945c-e2fefe18eae6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22149", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17474", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22149\n\ud83d\udd25 CVSS Score: 2.1 (cvssV4_0, 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)\n\ud83d\udd39 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).\n\ud83d\udccf Published: 2025-01-09T17:22:59.757Z\n\ud83d\udccf Modified: 2025-05-23T19:56:35.937Z\n\ud83d\udd17 References:\n1. https://github.com/MicahParks/jwkset/security/advisories/GHSA-675f-rq2r-jw82\n2. https://github.com/MicahParks/jwkset/issues/40\n3. https://github.com/MicahParks/jwkset/commit/01db49a90f7f20c7fb39a699a2f19a7a5f379ed3", "creation_timestamp": "2025-05-23T20:49:57.000000Z"}, {"uuid": "6d2564ba-7d95-4d30-a017-fb51cefcd894", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22149", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113799577018369526", "content": "", "creation_timestamp": "2025-01-09T17:29:01.619431Z"}, {"uuid": "4218b062-1d58-43e8-a3cb-7e2772861083", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22149", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfdbw6n43c25", "content": "", "creation_timestamp": "2025-01-09T18:15:59.041766Z"}, {"uuid": "b110a99d-f449-4c9f-a569-5464b323ee9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22149", "type": "seen", "source": "https://t.me/cvedetector/14879", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22149 - OpenJWKSetCacheReplacementVulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22149 \nPublished : Jan. 9, 2025, 6:15 p.m. | 43\u00a0minutes ago \nDescription : 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). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-09T20:16:37.000000Z"}, {"uuid": "1edf1637-82ba-4dc2-b99b-e934c4c0df0a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22149", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lfdd6stm7j2y", "content": "", "creation_timestamp": "2025-01-09T18:38:43.328843Z"}, {"uuid": "d274bb59-a284-4e7a-b174-b04fad3b3f29", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22149", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/996", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22149\n\ud83d\udd39 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).\n\ud83d\udccf Published: 2025-01-09T17:22:59.757Z\n\ud83d\udccf Modified: 2025-01-09T18:09:01.964Z\n\ud83d\udd17 References:\n1. https://github.com/MicahParks/jwkset/security/advisories/GHSA-675f-rq2r-jw82\n2. https://github.com/MicahParks/jwkset/issues/40\n3. https://github.com/MicahParks/jwkset/commit/01db49a90f7f20c7fb39a699a2f19a7a5f379ed3", "creation_timestamp": "2025-01-09T18:16:03.000000Z"}]}