<?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>Fri, 02 Oct 2026 14:21:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-243696</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-243696</link>
      <description>EUVD-2026-243696</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-243696</guid>
    </item>
    <item>
      <title>fkie_cve-2025-48879</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-48879</link>
      <description>&lt;p&gt;OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows any unauthenticated attacker to send a manipulated broken multipart/form-data request to OctoPrint and through that make the web server component become unresponsive. The issue can be triggered by a broken multipart/form-data request lacking an end boundary to any of OctoPrint&amp;#39;s endpoints implemented through the octoprint.server.util.tornado.UploadStorageFallbackHandler request handler. The request handler will get stuck in an endless busy loop, looking for a part of the request that will never come. As Tornado is single-threaded, that will effectively block the whole web server. The vulnerability has been patched in version 1.11.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows any unauthenticated attacker to send a manipulated broken multipart/form-data request to OctoPrint and through that make the web server component become unresponsive. The issue can be triggered by a broken multipart/form-data request lacking an end boundary to any of OctoPrint&amp;#39;s endpoints implemented through the octoprint.server.util.tornado.UploadStorageFallbackHandler request handler. The request handler will get stuck in an endless busy loop, looking for a part of the request that will never come. As Tornado is single-threaded, that will effectively block the whole web server. The vulnerability has been patched in version 1.11.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-48879</guid>
    </item>
    <item>
      <title>GHSA-9wj4-8h85-pgrw — OctoPrint Vulnerable to Denial of Service through malformed HTTP request in OctoPrint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9wj4-8h85-pgrw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: OctoPrint&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows any unauthenticated attacker to send a manipulated broken `multipart/form-data` request to OctoPrint and through that make the web server component become unresponsive. This could be used to effectively run a denial of service attack on the OctoPrint server.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been patched in version 1.11.2.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;OctoPrint administrators are once more reminded to not make OctoPrint available on hostile networks (e.g. the internet), regardless of whether this vulnerability is patched or not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The issue can be triggered by a broken `multipart/form-data` request lacking an end boundary to any of OctoPrint&amp;#39;s endpoints implemented through the `octoprint.server.util.tornado.UploadStorageFallbackHandler` request handler. The request handler will get stuck in an endless busy loop, looking for a part of the request that will never come. As Tornado is single-threaded, that will effectively block the whole web server.&lt;/p&gt;
&lt;p&gt;The fix adds detection of invalid requests like that and ensures they are handled gracefully with an HTTP 400 Bad Request response.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: OctoPrint&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows any unauthenticated attacker to send a manipulated broken `multipart/form-data` request to OctoPrint and through that make the web server component become unresponsive. This could be used to effectively run a denial of service attack on the OctoPrint server.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been patched in version 1.11.2.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;OctoPrint administrators are once more reminded to not make OctoPrint available on hostile networks (e.g. the internet), regardless of whether this vulnerability is patched or not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The issue can be triggered by a broken `multipart/form-data` request lacking an end boundary to any of OctoPrint&amp;#39;s endpoints implemented through the `octoprint.server.util.tornado.UploadStorageFallbackHandler` request handler. The request handler will get stuck in an endless busy loop, looking for a part of the request that will never come. As Tornado is single-threaded, that will effectively block the whole web server.&lt;/p&gt;
&lt;p&gt;The fix adds detection of invalid requests like that and ensures they are handled gracefully with an HTTP 400 Bad Request response.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9wj4-8h85-pgrw</guid>
    </item>
    <item>
      <title>PYSEC-2026-1713 — OctoPrint Vulnerable to Denial of Service through malformed HTTP request in OctoPrint</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1713</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: octoprint&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows any unauthenticated attacker to send a manipulated broken `multipart/form-data` request to OctoPrint and through that make the web server component become unresponsive. This could be used to effectively run a denial of service attack on the OctoPrint server.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been patched in version 1.11.2.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;OctoPrint administrators are once more reminded to not make OctoPrint available on hostile networks (e.g. the internet), regardless of whether this vulnerability is patched or not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The issue can be triggered by a broken `multipart/form-data` request lacking an end boundary to any of OctoPrint&amp;#39;s endpoints implemented through the `octoprint.server.util.tornado.UploadStorageFallbackHandler` request handler. The request handler will get stuck in an endless busy loop, looking for a part of the request that will never come. As Tornado is single-threaded, that will effectively block the whole web server.&lt;/p&gt;
&lt;p&gt;The fix adds detection of invalid requests like that and ensures they are handled gracefully with an HTTP 400 Bad Request response.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: octoprint&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;OctoPrint versions up until and including 1.11.1 contain a vulnerability that allows any unauthenticated attacker to send a manipulated broken `multipart/form-data` request to OctoPrint and through that make the web server component become unresponsive. This could be used to effectively run a denial of service attack on the OctoPrint server.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The vulnerability has been patched in version 1.11.2.&lt;/p&gt;
&lt;p&gt;### Workaround&lt;/p&gt;
&lt;p&gt;OctoPrint administrators are once more reminded to not make OctoPrint available on hostile networks (e.g. the internet), regardless of whether this vulnerability is patched or not.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The issue can be triggered by a broken `multipart/form-data` request lacking an end boundary to any of OctoPrint&amp;#39;s endpoints implemented through the `octoprint.server.util.tornado.UploadStorageFallbackHandler` request handler. The request handler will get stuck in an endless busy loop, looking for a part of the request that will never come. As Tornado is single-threaded, that will effectively block the whole web server.&lt;/p&gt;
&lt;p&gt;The fix adds detection of invalid requests like that and ensures they are handled gracefully with an HTTP 400 Bad Request response.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1713</guid>
    </item>
  </channel>
</rss>
