<?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>Mon, 16 Nov 2026 19:07:29 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1486 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1486</link>
      <description>certfr-2026-avi-1486</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1486</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-GS52627 — body-parser is body parsing middleware for Node</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-gs52627</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: argo-workflows&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the argo-workflows package. body-parser is body parsing middleware for Node.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: argo-workflows&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the argo-workflows package. body-parser is body parsing middleware for Node.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-gs52627</guid>
    </item>
    <item>
      <title>EUVD-2026-391229</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391229</link>
      <description>EUVD-2026-391229</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391229</guid>
    </item>
    <item>
      <title>fkie_cve-2026-111181</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-111181</link>
      <description>&lt;p&gt;body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-111181</guid>
    </item>
    <item>
      <title>GHSA-27r3-jxmh-p828 — body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-27r3-jxmh-p828</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: body-parser&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A single request can crash any application using `body-parser` with default options. When a request carries a `Content-Encoding` (for example `gzip`), `body-parser` pipes it into a decompression stream and, after reading the body, leaves that stream piped with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No authentication or matching route is required, since parsing runs before routing.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in body-parser 2.4.0 and 1.20.9. Upgrade to one of these versions.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Pass `inflate: false` to the body-parser middleware if the application does not need to accept compressed request bodies. This rejects encoded requests before any decompression stream is created.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: body-parser&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A single request can crash any application using `body-parser` with default options. When a request carries a `Content-Encoding` (for example `gzip`), `body-parser` pipes it into a decompression stream and, after reading the body, leaves that stream piped with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No authentication or matching route is required, since parsing runs before routing.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in body-parser 2.4.0 and 1.20.9. Upgrade to one of these versions.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Pass `inflate: false` to the body-parser middleware if the application does not need to accept compressed request bodies. This rejects encoded requests before any decompression stream is created.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-27r3-jxmh-p828</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-111181 — body-parser vulnerable to Denial of Service via trailing bytes after a compressed request body</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-111181</link>
      <description>msrc_CVE-2026-111181</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-111181</guid>
    </item>
    <item>
      <title>RHSA-2026:90388 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:90388</link>
      <description>&lt;p&gt;grafana: Grafana: Information disclosure via improper RBAC folder validation for deleted dashboards jose: jose: Denial of Service via unbounded decompression of crafted JWE tokens github.com/getkin/kin-openapi: kin-openapi: Denial of Service via improper handling of non-finite numeric values github.com/getkin/kin-openapi: kin-openapi: Denial of Service via nil-pointer dereference in request decoding github.com/getkin/kin-openapi: kin-openapi: Denial of Service via unbounded recursion during schema validation fast-uri: fast-uri: Path traversal via improper relative URI normalization fast-uri: fast-uri: Security policy bypass via improper host canonicalization fast-uri: fast-uri: Cross-Site Scripting via improper URI scheme decoding fast-uri: fast-uri: Cross-site scripting via unescaped colon in relative URI paths qs: qs: Denial of Service via unhandled exception during array serialization body-parser: body-parser: Denial of Service via unhandled decompression stream error&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;grafana: Grafana: Information disclosure via improper RBAC folder validation for deleted dashboards jose: jose: Denial of Service via unbounded decompression of crafted JWE tokens github.com/getkin/kin-openapi: kin-openapi: Denial of Service via improper handling of non-finite numeric values github.com/getkin/kin-openapi: kin-openapi: Denial of Service via nil-pointer dereference in request decoding github.com/getkin/kin-openapi: kin-openapi: Denial of Service via unbounded recursion during schema validation fast-uri: fast-uri: Path traversal via improper relative URI normalization fast-uri: fast-uri: Security policy bypass via improper host canonicalization fast-uri: fast-uri: Cross-Site Scripting via improper URI scheme decoding fast-uri: fast-uri: Cross-site scripting via unescaped colon in relative URI paths qs: qs: Denial of Service via unhandled exception during array serialization body-parser: body-parser: Denial of Service via unhandled decompression stream error&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:90388</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-111181</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-111181</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: node-body-parser, Ubuntu:18.04:LTS: node-body-parser, Ubuntu:20.04:LTS: node-body-parser, Ubuntu:22.04:LTS: node-body-parser, Ubuntu:24.04:LTS: node-body-parser, Ubuntu:26.10: node-body-parser, Ubuntu:26.04:LTS: node-body-parser&lt;/p&gt;
&lt;p&gt;body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: node-body-parser, Ubuntu:18.04:LTS: node-body-parser, Ubuntu:20.04:LTS: node-body-parser, Ubuntu:22.04:LTS: node-body-parser, Ubuntu:24.04:LTS: node-body-parser, Ubuntu:26.10: node-body-parser, Ubuntu:26.04:LTS: node-body-parser&lt;/p&gt;
&lt;p&gt;body-parser is body parsing middleware for Node.js and Express. In versions before 1.20.9 and in versions from 2.0.0 before 2.4.0, a single request can crash any application using body-parser with default options. When a request carries a Content-Encoding such as gzip, body-parser pipes it into a decompression stream and, after reading the body, leaves that stream with no error listener. A payload of one valid compressed frame followed by trailing bytes decodes and the application responds normally, but the trailing bytes then reach the already-finished decoder, which emits an error that is re-thrown as an uncaught exception and terminates the process. No matching route is required because body parsing runs before routing, so any endpoint that parses a body is affected. The issue is fixed in body-parser 2.4.0 and 1.20.9, and users should upgrade to one of those versions or later. As a workaround, disable request-body inflation (set the body-parser inflate option to false) so encoded requests are rejected before any decompression stream is created.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-111181</guid>
    </item>
  </channel>
</rss>
