<?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 entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 07:51:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-246691</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-246691</link>
      <description>EUVD-2026-246691</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-246691</guid>
    </item>
    <item>
      <title>fkie_cve-2025-53604</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53604</link>
      <description>&lt;p&gt;The web-push crate before 0.10.3 for Rust allows a denial of service (memory consumption) in the built-in clients via a large integer in a Content-Length header.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The web-push crate before 0.10.3 for Rust allows a denial of service (memory consumption) in the built-in clients via a large integer in a Content-Length header.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-53604</guid>
    </item>
    <item>
      <title>GHSA-287x-9rff-qvcg — Rust Web Push is vulnerable to a DoS attack via a large integer in a Content-Length header</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-287x-9rff-qvcg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: web-push&lt;/p&gt;
&lt;p&gt;The web-push crate before 0.10.4 for Rust allows a denial of service (memory consumption) in the built-in clients via a large integer in a Content-Length header. The patch was initially made available in version 0.10.3, but version 0.10.3 has since been yanked.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: web-push&lt;/p&gt;
&lt;p&gt;The web-push crate before 0.10.4 for Rust allows a denial of service (memory consumption) in the built-in clients via a large integer in a Content-Length header. The patch was initially made available in version 0.10.3, but version 0.10.3 has since been yanked.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-287x-9rff-qvcg</guid>
    </item>
    <item>
      <title>RUSTSEC-2025-0015 — Denial of Service via malicious Web Push endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2025-0015</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: web-push&lt;/p&gt;
&lt;p&gt;Prior to version 0.10.3, the built-in clients of the `web-push` crate
eagerly allocated memory based on the `Content-Length` header returned by the
Web Push endpoint. Malicious Web Push endpoints could return a large
`Content-Length` without ever having to send as much data, leading to
denial of service by memory exhaustion.&lt;/p&gt;
&lt;p&gt;Services providing Web Push notifications typically allow the user to
register an arbitrary endpoint, so the endpoint should not be trusted.&lt;/p&gt;
&lt;p&gt;The fixed version 0.10.3 now limits the amount of memory it will allocate
for each response, limits the amount of data it will read from the endpoint,
and returns an error if the endpoint sends too much data.&lt;/p&gt;
&lt;p&gt;As before, it is recommended that services add a timeout for each request
to Web Push endpoints.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: web-push&lt;/p&gt;
&lt;p&gt;Prior to version 0.10.3, the built-in clients of the `web-push` crate
eagerly allocated memory based on the `Content-Length` header returned by the
Web Push endpoint. Malicious Web Push endpoints could return a large
`Content-Length` without ever having to send as much data, leading to
denial of service by memory exhaustion.&lt;/p&gt;
&lt;p&gt;Services providing Web Push notifications typically allow the user to
register an arbitrary endpoint, so the endpoint should not be trusted.&lt;/p&gt;
&lt;p&gt;The fixed version 0.10.3 now limits the amount of memory it will allocate
for each response, limits the amount of data it will read from the endpoint,
and returns an error if the endpoint sends too much data.&lt;/p&gt;
&lt;p&gt;As before, it is recommended that services add a timeout for each request
to Web Push endpoints.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2025-0015</guid>
    </item>
  </channel>
</rss>
