Most recent entries from all

bdu:2026-10886

certfr-2026-avi-0500 — De multiples vulnérabilités ont été découvertes dans VMware Tanzu. Elles permettent à un attaquant de provoquer un prob…

certfr-2026-avi-0500

Withdrawn: CLEANSTART-2026-QW40696 — Security fixes in mongosh 2.8.2-r0

Withdrawn by the publisher.

Affected: CleanStart: mongosh

Package mongosh version 2.8.2-r0 fixes 23 vulnerabilities: ghsa-2w6w-674q-4c4q, ghsa-3mfm-83xf-c92r, ghsa-xhpv-hc6g-r9c6, ghsa-9cx6-37pm-9jff, ghsa-xjpj-3mr7-gcpf...

EUVD-2026-277969

fkie_cve-2026-33532

`yaml` is a YAML parser and serialiser for JavaScript. Parsing a YAML document with a version of `yaml` on the 1.x branch prior to 1.10.3 or on the 2.x branch prior to 2.8.3 may throw a RangeError due to a stack overflow. The node resolution/composition phase uses recursive function calls without a depth bound. An attacker who can supply YAML for parsing can trigger a `RangeError: Maximum call stack size exceeded` with a small payload (~2–10 KB). The `RangeError` is not a `YAMLParseError`, so applications that only catch YAML-specific errors will encounter an unexpected exception type. Depending on the host application's exception handling, this can fail requests or terminate the Node.js process. Flow sequences allow deep nesting with minimal bytes (2 bytes per level: one `[` and one `]`). On the default Node.js stack, approximately 1,000–5,000 levels of nesting (2–10 KB input) exhaust the call stack. The exact threshold is environment-dependent (Node.js version, stack size, call stack depth at invocation). Note: the library's `Parser` (CST phase) uses a stack-based iterative approach and is not affected. Only the compose/resolve phase uses actual call-stack recursion. All three public parsing APIs are affected: `YAML.parse()`, `YAML.parseDocument()`, and `YAML.parseAllDocuments()`. Versions 1.10.3 and 2.8.3 contain a patch.

GHSA-48c2-rrv3-qjmp — yaml is vulnerable to Stack Overflow via deeply nested YAML collections

Affected: npm: yaml

Parsing a YAML document with `yaml` may throw a RangeError due to a stack overflow.

The node resolution/composition phase uses recursive function calls without a depth bound. An attacker who can supply YAML for parsing can trigger a `RangeError: Maximum call stack size exceeded` with a small payload (~2–10 KB). The `RangeError` is not a `YAMLParseError`, so applications that only catch YAML-specific errors will encounter an unexpected exception type. Depending on the host application's exception handling, this can fail requests or terminate the Node.js process.

Flow sequences allow deep nesting with minimal bytes (2 bytes per level: one `[` and one `]`). On the default Node.js stack, approximately 1,000–5,000 levels of nesting (2–10 KB input) exhaust the call stack. The exact threshold is environment-dependent (Node.js version, stack size, call stack depth at invocation).

Note: the library's `Parser` (CST phase) uses a stack-based iterative approach and is not affected. Only the compose/resolve phase uses actual call-stack recursion.

All three public parsing APIs are affected: `YAML.parse()`, `YAML.parseDocument()`, and `YAML.parseAllDocuments()`.

### PoC

```javascript const YAML = require('yaml');

// ~10 KB payload: 5000 levels of nested flow sequences const payload = '['.repeat(5000) + '1' + ']'.repeat(5000);

try { YAML.parse(payload); } catch (e) { console.log(e.constructor.name); // RangeError (NOT YAMLParseError) console.log(e.message); // Maximum…

openSUSE-SU-2026:11053-1 — alloy-1.17.0-1.1 on GA media

alloy-1.17.0-1.1 on GA media

SUSE-SU-2026:22575-1 — Security update for alloy

Security update for alloy

UBUNTU-CVE-2026-33532

Affected: Ubuntu:22.04:LTS: node-yaml, Ubuntu:24.04:LTS: node-yaml, Ubuntu:25.10: node-yaml, Ubuntu:26.04:LTS: node-yaml

WID-SEC-W-2026-1407 — IBM App Connect Enterprise Certified Container: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise Certified Container ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.