{
  "cveId": "CVE-2026-33532",
  "url": "https://patchblox.com/security/cve/CVE-2026-33532",
  "summary": "CVE-2026-33532 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-33532, released March 26, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "node-yaml: \u0060yaml\u0060 is a YAML parser and serialiser for JavaScript",
  "description": "\u0060yaml\u0060 is a YAML parser and serialiser for JavaScript. Parsing a YAML document with a version of \u0060yaml\u0060 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 \u0060RangeError: Maximum call stack size exceeded\u0060 with a small payload (~2\u201310 KB). The \u0060RangeError\u0060 is not a \u0060YAMLParseError\u0060, so applications that only catch YAML-specific errors will encounter an unexpected exception type. Depending on the host application\u0027s 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 \u0060[\u0060 and one \u0060]\u0060). On the default Node.js stack, approximately 1,000\u20135,000 levels of nesting (2\u201310 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\u0027s \u0060Parser\u0060 (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: \u0060YAML.parse()\u0060, \u0060YAML.parseDocument()\u0060, and \u0060YAML.parseAllDocuments()\u0060. Versions 1.10.3 and 2.8.3 contain a patch.",
  "published": "2026-03-26T20:16:15Z",
  "severity": "medium",
  "cvss": 4.3,
  "cvssVector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
  "epss": 0.00488,
  "epssPercentile": 0.42287,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "alloy",
      "release": "opensuse-leap 16.0",
      "fixedVersion": "1.17.0-160000.1.1",
      "fix": "OPENSUSE-SU-2026:21251-1",
      "url": "https://patchblox.com/security/fix/linux/opensuse-su-2026-21251-1",
      "released": "2026-07-07T17:00:29Z"
    },
    {
      "platform": "linux",
      "product": "alloy",
      "release": "sles 15.7",
      "fixedVersion": "1.17.1-150700.15.23.1",
      "fix": "SUSE-SU-2026:2824-1",
      "url": "https://patchblox.com/security/fix/linux/suse-su-2026-2824-1",
      "released": "2026-07-09T18:18:01Z"
    },
    {
      "platform": "linux",
      "product": "alloy",
      "release": "sles 16.0",
      "fixedVersion": "1.17.0-160000.1.1",
      "fix": "SUSE-SU-2026:22575-1",
      "url": "https://patchblox.com/security/fix/linux/suse-su-2026-22575-1",
      "released": "2026-07-07T16:59:00Z"
    },
    {
      "platform": "linux",
      "product": "node-yaml",
      "release": "Debian 14",
      "fixedVersion": "2.8.3\u002B~cs0.4.0-1",
      "fix": "DEBIAN-CVE-2026-33532",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-33532",
      "released": "2026-03-26T20:16:15Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}