<?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 17:10:20 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1539 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1539</link>
      <description>certfr-2026-avi-1539</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1539</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-QP53856 — ### Summary



`qs</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-qp53856</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. ### Summary `qs.&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. ### Summary `qs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-qp53856</guid>
    </item>
    <item>
      <title>EUVD-2026-393867</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-393867</link>
      <description>EUVD-2026-393867</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-393867</guid>
    </item>
    <item>
      <title>fkie_cve-2026-110910</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-110910</link>
      <description>&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`qs.stringify` with `allowEmptyArrays: true` writes the key of an empty array without encoding it, even though keys are encoded by default. A key that contains `&amp;amp;` (or the configured `delimiter`), `=`, or `#` therefore becomes query string syntax instead of data, so a caller-supplied key name can add parameters to the serialized query string, or cut it short.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `lib/stringify.js`, the `allowEmptyArrays` branch returns `adjustedPrefix + &amp;#39;[]&amp;#39;` early, before the code that passes every other key through `encoder` and `formatter`. So `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [&amp;#34;1&amp;#34;] }` serializes as `x%26k%3Dv%5B0%5D=1`, but `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [] }` serializes as `x&amp;amp;k=v[]`. The early return applies at any depth (`{ &amp;#34;a&amp;#34;: { &amp;#34;b&amp;amp;k=v&amp;#34;: [] } }` gives `a[b&amp;amp;k=v][]`), under every `arrayFormat`, with `allowDots`, and with a custom `encoder`, which is never called for that key. With `encode: false` or `encodeValuesOnly: true`, keys are intentionally left unencoded on every path; those configurations are not affected.&lt;/p&gt;
&lt;p&gt;#### PoC&lt;/p&gt;
&lt;p&gt;```js&lt;/p&gt;
&lt;p&gt;var qs = require(&amp;#34;qs&amp;#34;);&lt;/p&gt;
&lt;p&gt;var query = qs.stringify({ q: &amp;#34;hi&amp;#34;, &amp;#34;x&amp;amp;apiKey=evil&amp;amp;y&amp;#34;: [] }, { allowEmptyArrays: true });&lt;/p&gt;
&lt;p&gt;// &amp;#34;q=hi&amp;amp;x&amp;amp;apiKey=evil&amp;amp;y[]&amp;#34;&lt;/p&gt;
&lt;p&gt;qs.parse(query);&lt;/p&gt;
&lt;p&gt;// { q: &amp;#34;hi&amp;#34;, x: &amp;#34;&amp;#34;, apiKey: &amp;#34;evil&amp;#34;, y: [&amp;#34;&amp;#34;] }&lt;/p&gt;
&lt;p&gt;qs.stringify({ &amp;#34;x#&amp;#34;: [], z: &amp;#34;1&amp;#34; }, { allowEmptyArrays: true });&lt;/p&gt;
&lt;p&gt;// &amp;#34;x#[]&amp;amp;z=1&amp;#34;: in a URL, everything after &amp;#34;#&amp;#34; becomes the fragment&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;#### Fix&lt;/p&gt;
&lt;p&gt;Applied in 234d505 on `main` and released as v6.17.0, and backported to v6.16.2, v6.15…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`qs.stringify` with `allowEmptyArrays: true` writes the key of an empty array without encoding it, even though keys are encoded by default. A key that contains `&amp;amp;` (or the configured `delimiter`), `=`, or `#` therefore becomes query string syntax instead of data, so a caller-supplied key name can add parameters to the serialized query string, or cut it short.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `lib/stringify.js`, the `allowEmptyArrays` branch returns `adjustedPrefix + &amp;#39;[]&amp;#39;` early, before the code that passes every other key through `encoder` and `formatter`. So `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [&amp;#34;1&amp;#34;] }` serializes as `x%26k%3Dv%5B0%5D=1`, but `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [] }` serializes as `x&amp;amp;k=v[]`. The early return applies at any depth (`{ &amp;#34;a&amp;#34;: { &amp;#34;b&amp;amp;k=v&amp;#34;: [] } }` gives `a[b&amp;amp;k=v][]`), under every `arrayFormat`, with `allowDots`, and with a custom `encoder`, which is never called for that key. With `encode: false` or `encodeValuesOnly: true`, keys are intentionally left unencoded on every path; those configurations are not affected.&lt;/p&gt;
&lt;p&gt;#### PoC&lt;/p&gt;
&lt;p&gt;```js&lt;/p&gt;
&lt;p&gt;var qs = require(&amp;#34;qs&amp;#34;);&lt;/p&gt;
&lt;p&gt;var query = qs.stringify({ q: &amp;#34;hi&amp;#34;, &amp;#34;x&amp;amp;apiKey=evil&amp;amp;y&amp;#34;: [] }, { allowEmptyArrays: true });&lt;/p&gt;
&lt;p&gt;// &amp;#34;q=hi&amp;amp;x&amp;amp;apiKey=evil&amp;amp;y[]&amp;#34;&lt;/p&gt;
&lt;p&gt;qs.parse(query);&lt;/p&gt;
&lt;p&gt;// { q: &amp;#34;hi&amp;#34;, x: &amp;#34;&amp;#34;, apiKey: &amp;#34;evil&amp;#34;, y: [&amp;#34;&amp;#34;] }&lt;/p&gt;
&lt;p&gt;qs.stringify({ &amp;#34;x#&amp;#34;: [], z: &amp;#34;1&amp;#34; }, { allowEmptyArrays: true });&lt;/p&gt;
&lt;p&gt;// &amp;#34;x#[]&amp;amp;z=1&amp;#34;: in a URL, everything after &amp;#34;#&amp;#34; becomes the fragment&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;#### Fix&lt;/p&gt;
&lt;p&gt;Applied in 234d505 on `main` and released as v6.17.0, and backported to v6.16.2, v6.15…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-110910</guid>
    </item>
    <item>
      <title>RHSA-2026:94794 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:94794</link>
      <description>&lt;p&gt;qs: qs: Query parameter injection via unencoded empty array keys github.com/klauspost/compress/zstd: klauspost/compress: Denial of Service via crafted zstd compressed input follow-redirects: follow-redirects: Information disclosure via cross-origin redirects&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;qs: qs: Query parameter injection via unencoded empty array keys github.com/klauspost/compress/zstd: klauspost/compress: Denial of Service via crafted zstd compressed input follow-redirects: follow-redirects: Information disclosure via cross-origin redirects&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:94794</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-110910</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-110910</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: node-qs, Ubuntu:16.04:LTS: node-qs, Ubuntu:18.04:LTS: node-qs, Ubuntu:Pro:20.04:LTS: node-qs, Ubuntu:22.04:LTS: node-qs, Ubuntu:24.04:LTS: node-qs, Ubuntu:26.10: node-qs, Ubuntu:26.04:LTS: node-qs&lt;/p&gt;
&lt;p&gt;### Summary `qs.stringify` with `allowEmptyArrays: true` writes the key of an empty array without encoding it, even though keys are encoded by default. A key that contains `&amp;amp;` (or the configured `delimiter`), `=`, or `#` therefore becomes query string syntax instead of data, so a caller-supplied key name can add parameters to the serialized query string, or cut it short. ### Details In `lib/stringify.js`, the `allowEmptyArrays` branch returns `adjustedPrefix + &amp;#39;[]&amp;#39;` early, before the code that passes every other key through `encoder` and `formatter`. So `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [&amp;#34;1&amp;#34;] }` serializes as `x%26k%3Dv%5B0%5D=1`, but `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [] }` serializes as `x&amp;amp;k=v[]`. The early return applies at any depth (`{ &amp;#34;a&amp;#34;: { &amp;#34;b&amp;amp;k=v&amp;#34;: [] } }` gives `a[b&amp;amp;k=v][]`), under every `arrayFormat`, with `allowDots`, and with a custom `encoder`, which is never called for that key. With `encode: false` or `encodeValuesOnly: true`, keys are intentionally left unencoded on every path; those configurations are not affected. #### PoC ```js var qs = require(&amp;#34;qs&amp;#34;); var query = qs.stringify({ q: &amp;#34;hi&amp;#34;, &amp;#34;x&amp;amp;apiKey=evil&amp;amp;y&amp;#34;: [] }, { allowEmptyArrays: true }); // &amp;#34;q=hi&amp;amp;x&amp;amp;apiKey=evil&amp;amp;y[]&amp;#34; qs.parse(query); // { q: &amp;#34;hi&amp;#34;, x: &amp;#34;&amp;#34;, apiKey: &amp;#34;evil&amp;#34;, y: [&amp;#34;&amp;#34;] } qs.stringify({ &amp;#34;x#&amp;#34;: [], z: &amp;#34;1&amp;#34; }, { allowEmptyArrays: true }); // &amp;#34;x#[]&amp;amp;z=1&amp;#34;: in a URL, everything after &amp;#34;#&amp;#34; becomes the fragment ``` #### Fix Applied in 234d505 on `main` and released as v6.17.0, and backported to v6.16.2, v6.15.4, v6.14.3, v6.13.4, and v6.12.6: the key of…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: node-qs, Ubuntu:16.04:LTS: node-qs, Ubuntu:18.04:LTS: node-qs, Ubuntu:Pro:20.04:LTS: node-qs, Ubuntu:22.04:LTS: node-qs, Ubuntu:24.04:LTS: node-qs, Ubuntu:26.10: node-qs, Ubuntu:26.04:LTS: node-qs&lt;/p&gt;
&lt;p&gt;### Summary `qs.stringify` with `allowEmptyArrays: true` writes the key of an empty array without encoding it, even though keys are encoded by default. A key that contains `&amp;amp;` (or the configured `delimiter`), `=`, or `#` therefore becomes query string syntax instead of data, so a caller-supplied key name can add parameters to the serialized query string, or cut it short. ### Details In `lib/stringify.js`, the `allowEmptyArrays` branch returns `adjustedPrefix + &amp;#39;[]&amp;#39;` early, before the code that passes every other key through `encoder` and `formatter`. So `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [&amp;#34;1&amp;#34;] }` serializes as `x%26k%3Dv%5B0%5D=1`, but `{ &amp;#34;x&amp;amp;k=v&amp;#34;: [] }` serializes as `x&amp;amp;k=v[]`. The early return applies at any depth (`{ &amp;#34;a&amp;#34;: { &amp;#34;b&amp;amp;k=v&amp;#34;: [] } }` gives `a[b&amp;amp;k=v][]`), under every `arrayFormat`, with `allowDots`, and with a custom `encoder`, which is never called for that key. With `encode: false` or `encodeValuesOnly: true`, keys are intentionally left unencoded on every path; those configurations are not affected. #### PoC ```js var qs = require(&amp;#34;qs&amp;#34;); var query = qs.stringify({ q: &amp;#34;hi&amp;#34;, &amp;#34;x&amp;amp;apiKey=evil&amp;amp;y&amp;#34;: [] }, { allowEmptyArrays: true }); // &amp;#34;q=hi&amp;amp;x&amp;amp;apiKey=evil&amp;amp;y[]&amp;#34; qs.parse(query); // { q: &amp;#34;hi&amp;#34;, x: &amp;#34;&amp;#34;, apiKey: &amp;#34;evil&amp;#34;, y: [&amp;#34;&amp;#34;] } qs.stringify({ &amp;#34;x#&amp;#34;: [], z: &amp;#34;1&amp;#34; }, { allowEmptyArrays: true }); // &amp;#34;x#[]&amp;amp;z=1&amp;#34;: in a URL, everything after &amp;#34;#&amp;#34; becomes the fragment ``` #### Fix Applied in 234d505 on `main` and released as v6.17.0, and backported to v6.16.2, v6.15.4, v6.14.3, v6.13.4, and v6.12.6: the key of…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-110910</guid>
    </item>
  </channel>
</rss>
