<?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://vulnerability.circl.lu</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>Tue, 09 Jun 2026 01:53:02 +0000</lastBuildDate>
    <item>
      <title>a6182154-1172-4f9e-9550-00a88679dadb</title>
      <link>https://vulnerability.circl.lu/sighting/a6182154-1172-4f9e-9550-00a88679dadb/export</link>
      <description>{"uuid": "a6182154-1172-4f9e-9550-00a88679dadb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-47270", "type": "seen", "source": "https://t.me/cvedetector/25073", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-47270 - Nimiq Albatross Denial of Service Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-47270 \nPublished : May 12, 2025, 11:15 a.m. | 1\u00a0hour ago \nDescription : nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. The `nimiq-network-libp2p` subcrate of nimiq/core-rs-albatross is vulnerable to a Denial of Service (DoS) attack due to uncontrolled memory allocation. Specifically, the implementation of the `Discovery` network message handling allocates a buffer based on a length value provided by the peer, without enforcing an upper bound. Since this length is a `u32`, a peer can trigger allocations of up to 4 GB, potentially leading to memory exhaustion and node crashes. As Discovery messages are regularly exchanged for peer discovery, this vulnerability can be exploited repeatedly. The patch for this vulnerability is formally released as part of v1.1.0. The patch implements a limit to the discovery message size of 1 MB and also resizes the message buffer size incrementally as the data is read. No known workarounds are available. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"12 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-12T14:26:21.000000Z"}</description>
      <content:encoded>{"uuid": "a6182154-1172-4f9e-9550-00a88679dadb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-47270", "type": "seen", "source": "https://t.me/cvedetector/25073", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-47270 - Nimiq Albatross Denial of Service Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-47270 \nPublished : May 12, 2025, 11:15 a.m. | 1\u00a0hour ago \nDescription : nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. The `nimiq-network-libp2p` subcrate of nimiq/core-rs-albatross is vulnerable to a Denial of Service (DoS) attack due to uncontrolled memory allocation. Specifically, the implementation of the `Discovery` network message handling allocates a buffer based on a length value provided by the peer, without enforcing an upper bound. Since this length is a `u32`, a peer can trigger allocations of up to 4 GB, potentially leading to memory exhaustion and node crashes. As Discovery messages are regularly exchanged for peer discovery, this vulnerability can be exploited repeatedly. The patch for this vulnerability is formally released as part of v1.1.0. The patch implements a limit to the discovery message size of 1 MB and also resizes the message buffer size incrementally as the data is read. No known workarounds are available. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"12 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-12T14:26:21.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/a6182154-1172-4f9e-9550-00a88679dadb/export</guid>
      <pubDate>Mon, 12 May 2025 14:26:21 +0000</pubDate>
    </item>
    <item>
      <title>526e5243-e402-44c2-ab54-a568da82134b</title>
      <link>https://vulnerability.circl.lu/sighting/526e5243-e402-44c2-ab54-a568da82134b/export</link>
      <description>{"uuid": "526e5243-e402-44c2-ab54-a568da82134b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-47270", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loy7duqxwj2h", "content": "", "creation_timestamp": "2025-05-12T14:42:39.463831Z"}</description>
      <content:encoded>{"uuid": "526e5243-e402-44c2-ab54-a568da82134b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-47270", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loy7duqxwj2h", "content": "", "creation_timestamp": "2025-05-12T14:42:39.463831Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/526e5243-e402-44c2-ab54-a568da82134b/export</guid>
      <pubDate>Mon, 12 May 2025 14:42:39 +0000</pubDate>
    </item>
  </channel>
</rss>
