chore(deps): update dependency yaml to v2.8.3 [security]#58
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency yaml to v2.8.3 [security]#58renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
April 1, 2026 17:02
5d2bd21 to
3dd408e
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
April 8, 2026 14:39
3dd408e to
7632116
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
April 29, 2026 13:41
7632116 to
630866f
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
May 12, 2026 09:48
630866f to
41236e6
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
May 18, 2026 12:36
41236e6 to
788ead4
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
May 28, 2026 15:48
788ead4 to
d9d65e5
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
June 1, 2026 20:15
d9d65e5 to
16167ea
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
June 13, 2026 16:02
16167ea to
b6430a8
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
July 12, 2026 12:46
b6430a8 to
49ebc36
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
July 16, 2026 17:23
49ebc36 to
f61de09
Compare
renovate
Bot
force-pushed
the
renovate/npm-yaml-vulnerability
branch
from
July 21, 2026 02:30
f61de09 to
6ca9798
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.3.1→2.8.3yaml is vulnerable to Stack Overflow via deeply nested YAML collections
CVE-2026-33532 / GHSA-48c2-rrv3-qjmp
More information
Details
Parsing a YAML document with
yamlmay 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 exceededwith a small payload (~2–10 KB). TheRangeErroris not aYAMLParseError, 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(), andYAML.parseAllDocuments().PoC
Test environment: Node.js v24.12.0, macOS darwin arm64
Depth threshold on yaml 2.8.2:
Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
eemeli/yaml (yaml)
v2.8.3Compare Source
trailingCommaToString option for multiline flow formatting (#670)1e84ebb)v2.8.2Compare Source
v2.8.1Compare Source
v2.8.0Compare Source
--mergeoption to CLI tool (#611)v2.7.1Compare Source
v2.7.0Compare Source
The library is now available on JSR as @eemeli/yaml and on deno.land/x as yaml. In addition to Node.js and browsers, it should work in Deno, Bun, and Cloudflare Workers.
v2.6.1Compare Source
:00seconds from!!timestampvalues (#578, with thanks to @qraynaud)!!bool(#587, with thanks to @vra5107)v2.6.0Compare Source
!!merge <<keys (#580)stringKeysparse option (#581)v2.5.1Compare Source
v2.5.0Compare Source
--indentoption to CLI tool (#559, with thanks to @danielbayley)...(#558)minContentWidthif greater thanlineWidth(#562)Collection.maxFlowStringSingleLineLength(#522, #421)v2.4.5Compare Source
v2.4.4Compare Source
With special thanks to @RedCMD for finding and reporting all of the following:
[]{}immediately after:with plain key (#550)?explicit-key contents (#551)v2.4.3Compare Source
-.NaNor+.nanas NaN (#546)#within%TAGprefixes with trailing#commentsv2.4.2Compare Source
v2.4.1Compare Source
v2.4.0Compare Source
lineWidthoption for line breaking in flow collections (#522)v2.3.4Compare Source
v2.3.3Compare Source
v2.3.2Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.