Debian Package Tracker
Register | Log in
Subscribe

node-yaml

Nodejs parser and stringifier for YAML standard

Choose email to subscribe with

general
  • source: node-yaml (main)
  • version: 2.8.3+~cs0.4.0-1
  • maintainer: Debian Javascript Maintainers (archive) (DMD)
  • uploaders: Yadd [DMD]
  • arch: all
  • std-ver: 4.7.3
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 1.10.0-4
  • oldstable: 2.1.3-2
  • stable: 2.3.4+~cs0.4.0-1
  • testing: 2.8.3+~cs0.4.0-1
  • unstable: 2.8.3+~cs0.4.0-1
versioned links
  • 1.10.0-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.1.3-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.3.4+~cs0.4.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.8.3+~cs0.4.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • node-yaml
action needed
A new upstream version is available: 3.0.0-0+~cs0.4.0 high
A new upstream version 3.0.0-0+~cs0.4.0 is available, you should consider packaging it.
Created: 2026-02-17 Last update: 2026-04-08 03:30
1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:
  • 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.
Created: 2026-03-27 Last update: 2026-04-02 11:18
1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:
  • 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.
Created: 2026-03-27 Last update: 2026-04-02 11:18
1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:
  • 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.
Created: 2026-03-27 Last update: 2026-04-02 11:18
lintian reports 2 warnings normal
Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2024-08-02 Last update: 2026-03-28 03:31
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.3).
Created: 2026-03-31 Last update: 2026-03-31 15:01
news
[rss feed]
  • [2026-04-03] node-yaml 2.8.3+~cs0.4.0-1 MIGRATED to testing (Debian testing watch)
  • [2026-03-27] Accepted node-yaml 2.8.3+~cs0.4.0-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2025-12-18] node-yaml 2.8.2+~cs0.4.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-12-15] Accepted node-yaml 2.8.2+~cs0.4.0-1 (source) into unstable (Jérémy Lal)
  • [2024-08-03] node-yaml 2.3.4+~cs0.4.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-08-01] Accepted node-yaml 2.3.4+~cs0.4.0-1 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
  • [2023-11-14] node-yaml 2.3.4-1 MIGRATED to testing (Debian testing watch)
  • [2023-11-12] Accepted node-yaml 2.3.4-1 (source) into unstable (Godwin Nweke) (signed by: Xavier Guimard)
  • [2023-08-16] node-yaml 2.3.1-2 MIGRATED to testing (Debian testing watch)
  • [2023-08-13] Accepted node-yaml 2.3.1-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2023-07-16] Accepted node-yaml 2.3.1-1 (source) into experimental (Yadd) (signed by: Xavier Guimard)
  • [2023-05-12] node-yaml 2.1.3-2 MIGRATED to testing (Debian testing watch)
  • [2023-05-06] Accepted node-yaml 2.1.3-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-10-31] node-yaml 2.1.3-1 MIGRATED to testing (Debian testing watch)
  • [2022-10-29] Accepted node-yaml 2.1.3-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-10-28] Accepted node-yaml 2.1.2-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-10-06] node-yaml 2.1.2-1 MIGRATED to testing (Debian testing watch)
  • [2022-10-03] Accepted node-yaml 2.1.2-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-07-26] node-yaml 2.1.1-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-21] Accepted node-yaml 2.1.1-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-05-08] node-yaml 2.0.1-2 MIGRATED to testing (Debian testing watch)
  • [2022-05-04] Accepted node-yaml 2.0.1-2 (source) into unstable (Jérémy Lal)
  • [2022-05-03] Accepted node-yaml 2.0.1-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2021-11-24] node-yaml 1.10.2-1 MIGRATED to testing (Debian testing watch)
  • [2021-11-22] Accepted node-yaml 1.10.2-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2021-02-03] Accepted node-yaml 1.10.0-4~bpo10+1 (source all) into buster-backports, buster-backports (Debian FTP Masters) (signed by: Praveen Arimbrathodiyil)
  • [2021-01-16] node-yaml 1.10.0-4 MIGRATED to testing (Debian testing watch)
  • [2021-01-13] Accepted node-yaml 1.10.0-4 (source) into unstable (Xavier Guimard)
  • [2021-01-13] Accepted node-yaml 1.10.0-3 (source) into unstable (Xavier Guimard)
  • [2020-11-26] node-yaml 1.10.0-2 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian (0, 2)
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.8.3+~cs0.4.0-1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing