<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 04 May 2026 11:51:30 +0000</lastBuildDate>
    <item>
      <title>03d798a2-d110-450c-8c11-fadf5b8fd315</title>
      <link>https://db.gcve.eu/sighting/03d798a2-d110-450c-8c11-fadf5b8fd315/export</link>
      <description>{"uuid": "03d798a2-d110-450c-8c11-fadf5b8fd315", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-675f-rq2r-jw82", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113799577018369526", "content": "", "creation_timestamp": "2025-01-09T17:29:01.658932Z"}</description>
      <content:encoded>{"uuid": "03d798a2-d110-450c-8c11-fadf5b8fd315", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-675f-rq2r-jw82", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113799577018369526", "content": "", "creation_timestamp": "2025-01-09T17:29:01.658932Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/03d798a2-d110-450c-8c11-fadf5b8fd315/export</guid>
      <pubDate>Thu, 09 Jan 2025 17:29:01 +0000</pubDate>
    </item>
    <item>
      <title>50f9da46-311e-4970-b4dc-0b866e6f3ffd</title>
      <link>https://db.gcve.eu/sighting/50f9da46-311e-4970-b4dc-0b866e6f3ffd/export</link>
      <description>{"uuid": "50f9da46-311e-4970-b4dc-0b866e6f3ffd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-675F-RQ2R-JW82", "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"}</description>
      <content:encoded>{"uuid": "50f9da46-311e-4970-b4dc-0b866e6f3ffd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-675F-RQ2R-JW82", "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"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/50f9da46-311e-4970-b4dc-0b866e6f3ffd/export</guid>
      <pubDate>Thu, 09 Jan 2025 18:16:03 +0000</pubDate>
    </item>
    <item>
      <title>80c8ae8c-5742-405d-ac2b-99edfc9bb452</title>
      <link>https://db.gcve.eu/sighting/80c8ae8c-5742-405d-ac2b-99edfc9bb452/export</link>
      <description>{"uuid": "80c8ae8c-5742-405d-ac2b-99edfc9bb452", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-675F-RQ2R-JW82", "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"}</description>
      <content:encoded>{"uuid": "80c8ae8c-5742-405d-ac2b-99edfc9bb452", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-675F-RQ2R-JW82", "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"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/80c8ae8c-5742-405d-ac2b-99edfc9bb452/export</guid>
      <pubDate>Fri, 23 May 2025 20:49:57 +0000</pubDate>
    </item>
  </channel>
</rss>
