<?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 12:31:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-67213 — nanoid before 5.1.6 Infinite Loop via Zero Size in customAlphabet and customRandom</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-67213</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nanoid_project nanoid&lt;/p&gt;
&lt;p&gt;nanoid (Nano ID) before 5.1.6 contains an infinite loop in the customAlphabet and customRandom functions. When these functions are configured with a size of 0, the internal generation loop never satisfies its exit condition and spins indefinitely, hanging the calling thread. An application that passes an unvalidated, attacker-controlled size of 0 to these functions is exposed to a denial-of-service condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nanoid_project nanoid&lt;/p&gt;
&lt;p&gt;nanoid (Nano ID) before 5.1.6 contains an infinite loop in the customAlphabet and customRandom functions. When these functions are configured with a size of 0, the internal generation loop never satisfies its exit condition and spins indefinitely, hanging the calling thread. An application that passes an unvalidated, attacker-controlled size of 0 to these functions is exposed to a denial-of-service condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-67213</guid>
    </item>
    <item>
      <title>GHSA-5p4m-2wfm-xmqj — JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5p4m-2wfm-xmqj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: js-yaml&lt;/p&gt;
&lt;p&gt;# Quadratic CPU consumption in `!!omap` resolution (js-yaml 3.x and 4.x)&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`resolveYamlOmap()` enforces key uniqueness for `!!omap` sequences with a linear
scan (`objectKeys.indexOf(...)`) inside the per-element loop, making resolution
**O(n²)** in the number of entries. A modestly sized YAML document therefore
consumes disproportionate CPU inside `yaml.load()`, giving a denial of service
against any consumer that parses untrusted YAML.&lt;/p&gt;
&lt;p&gt;`!!omap` is registered in the **default schema**
(`lib/schema/default.js` → `require(&amp;#39;../type/omap&amp;#39;)`), so a plain
`yaml.load(untrustedInput)` with no options is affected — no custom schema or
non-default configuration is required.&lt;/p&gt;
&lt;p&gt;**This is the same weakness as CVE-2026-59870 / GHSA-724g-mxrg-4qvm**, which was
fixed in the 5.x line in 5.2.1. That fix was never backported: both currently
maintained legacy lines still carry the original implementation.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;| Line | Latest tested | Status |
|---|---|---|
| 3.x | **3.15.0** | Affected — `objectKeys.indexOf(pairKey)` at `lib/type/omap.js:29` |
| 4.x | **4.3.0** | Affected — `objectKeys.indexOf(pairKey)` at `lib/type/omap.js:30` |
| 5.x | 5.2.2 | **Not affected** — fixed in 5.2.1 (uses a `Set`) |&lt;/p&gt;
&lt;p&gt;Both figures are the newest release of each line at the time of writing, so
this is not a &amp;#34;you are on an old version&amp;#34; issue.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`lib/type/omap.js` (js-yaml 4.3.0):&lt;/p&gt;
&lt;p&gt;```js
if (objectKeys.indexOf(pairKey) === -1) objectKeys.push(pairKey)
else return false
```&lt;/p&gt;
&lt;p&gt;`obj…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: js-yaml&lt;/p&gt;
&lt;p&gt;# Quadratic CPU consumption in `!!omap` resolution (js-yaml 3.x and 4.x)&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`resolveYamlOmap()` enforces key uniqueness for `!!omap` sequences with a linear
scan (`objectKeys.indexOf(...)`) inside the per-element loop, making resolution
**O(n²)** in the number of entries. A modestly sized YAML document therefore
consumes disproportionate CPU inside `yaml.load()`, giving a denial of service
against any consumer that parses untrusted YAML.&lt;/p&gt;
&lt;p&gt;`!!omap` is registered in the **default schema**
(`lib/schema/default.js` → `require(&amp;#39;../type/omap&amp;#39;)`), so a plain
`yaml.load(untrustedInput)` with no options is affected — no custom schema or
non-default configuration is required.&lt;/p&gt;
&lt;p&gt;**This is the same weakness as CVE-2026-59870 / GHSA-724g-mxrg-4qvm**, which was
fixed in the 5.x line in 5.2.1. That fix was never backported: both currently
maintained legacy lines still carry the original implementation.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;| Line | Latest tested | Status |
|---|---|---|
| 3.x | **3.15.0** | Affected — `objectKeys.indexOf(pairKey)` at `lib/type/omap.js:29` |
| 4.x | **4.3.0** | Affected — `objectKeys.indexOf(pairKey)` at `lib/type/omap.js:30` |
| 5.x | 5.2.2 | **Not affected** — fixed in 5.2.1 (uses a `Set`) |&lt;/p&gt;
&lt;p&gt;Both figures are the newest release of each line at the time of writing, so
this is not a &amp;#34;you are on an old version&amp;#34; issue.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;`lib/type/omap.js` (js-yaml 4.3.0):&lt;/p&gt;
&lt;p&gt;```js
if (objectKeys.indexOf(pairKey) === -1) objectKeys.push(pairKey)
else return false
```&lt;/p&gt;
&lt;p&gt;`obj…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5p4m-2wfm-xmqj</guid>
    </item>
  </channel>
</rss>
