deps(openapi-helpers): update dependency yaml to v2.8.3 [security] - abandoned#169
Open
mapcolonies-devops wants to merge 7 commits intomasterfrom
Open
deps(openapi-helpers): update dependency yaml to v2.8.3 [security] - abandoned#169mapcolonies-devops wants to merge 7 commits intomasterfrom
mapcolonies-devops wants to merge 7 commits intomasterfrom
Conversation
Release-As: 4.1.0
* chore(global): release express-access-log-middleware 5.0.0 * chore(express-access-log-middleware): fix release --------- Co-authored-by: CptSchnitz <12687466+CptSchnitz@users.noreply.github.com>
* chore(global): release js-logger 4.1.0 * chore(js-logger): fix release --------- Co-authored-by: CptSchnitz <12687466+CptSchnitz@users.noreply.github.com>
Contributor
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
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.8.2→2.8.3GitHub Vulnerability Alerts
CVE-2026-33532
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:
Release Notes
eemeli/yaml (yaml)
v2.8.3Compare Source
trailingCommaToString option for multiline flow formatting (#670)1e84ebb)Configuration
📅 Schedule: Branch creation - "" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 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 has been generated by Renovate Bot.