---
title: "yaml 2.9.1: release notes, upgrades and advisories"
description: "yaml 2.9.1: release notes, breaking changes by major version and 2 known advisories with their fix."
url: https://inlinr.com/packages/yaml
lang: en
---

[Packages](https://inlinr.com/packages)

# yaml

2.9.1 · 11 Sep 2026 ISC 330.2M / week [Repository](https://github.com/eemeli/yaml) [Homepage](https://eemeli.org/yaml/) [npm](https://www.npmjs.com/package/yaml) [Atom feed](https://inlinr.com/packages/feed/yaml)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/yaml/upgrade)

LineNewestSecurity

- 2.x 2.9.1 Safe from 2.8.3 Latest line
- 1.x 1.10.3 Safe from 1.10.3 [To 2.9.1](https://inlinr.com/packages/yaml/upgrade/1.10.3-2.9.1)
- 0.x 0.3.0 No known advisory [To 2.9.1](https://inlinr.com/packages/yaml/upgrade/0.3.0-2.9.1)

## Latest releases

[All 69 releases](https://inlinr.com/packages/yaml/releases)

1. 2.x · latest line
2. ### [2.9.1](https://inlinr.com/packages/yaml/releases/2.9.1 "Open this release") [](https://github.com/eemeli/yaml/releases/tag/v2.9.1 "Read this release where it was published")  
11 Sep 2026

  - Limit recursive merge aliases ([#685](https://github.com/eemeli/yaml/issues/685), [#713](https://github.com/eemeli/yaml/issues/713))
  - Simplify line unfolding during quoted string parsing
3. ### [2.9.0](https://inlinr.com/packages/yaml/releases/2.9.0 "Open this release") [](https://github.com/eemeli/yaml/releases/tag/v2.9.0 "Read this release where it was published")  
11 May 2026

  - Avoid calling `Array.prototype.push.apply()` with large source array
  - **lexer:** Avoid recursive calls that may exhaust the call stack
4. ### [2.8.4](https://inlinr.com/packages/yaml/releases/2.8.4 "Open this release") [](https://github.com/eemeli/yaml/releases/tag/v2.8.4 "Read this release where it was published")  
2 May 2026

  - Disable alias resolution with `maxAliasCount:0`
  - Handle invalid unicode escapes
  - Apply `minFractionDigits` only to decimal strings

Dependency tracking

## Know when your own dependencies move

yaml had 1 security advisory in the last 12 months. inlinr emails you the day one touches a project of yours, with the version that fixes it.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

[Details](https://inlinr.com/packages/yaml/security)

- [Uncaught Exception in yaml](https://inlinr.com/advisories/GHSA-f9xv-q969-pqx4) High · fixed in 2.2.2
- [yaml is vulnerable to Stack Overflow via deeply nested YAML collections](https://inlinr.com/advisories/GHSA-48c2-rrv3-qjmp) Moderate · fixed in 2.8.3, 1.10.3

## Health of 2.9.1

[Details](https://inlinr.com/packages/yaml/security#signals)

- **Provenance**: None
- **Publisher**: eemeli
- **Maintainers**: 1
- **Scorecard**: 8 / 10
- **Size**: 686 kB

## Weekly downloads

Registry facts last checked 11 Nov 2026\. Releases and advisories last read 22 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
