chore(deps): update dependency js-yaml [security] #6052
+57
−24
Conversation
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
backstage-goalie
bot
added
dependencies
backstage-goalie
bot
requested a review
from christoph-jerolimov
as a code owner
backstage-goalie
bot
added
the
dependencies
backstage-goalie
bot
requested review from
ciiay and
debsmita1
as code owners
backstage-goalie
bot
requested review from
a team,
AndrienkoAleksandr,
PatAKnight,
aljesusg,
awanlin,
backstage-service,
divyanshiGupta,
dzemanov,
josunect,
leandroberetta and
logonoff
as code owners
backstage-service
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
eafa50d to
f2b72ca
Compare
logonoff
approved these changes
Nov 14, 2025
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
f2b72ca to
43e5d2d
Compare
backstage-service
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
43e5d2d to
7cfab4e
Compare
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
7cfab4e to
e710137
Compare
backstage-goalie
bot
changed the title
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
2 times, most recently
from
06d3d87 to
da19170
Compare
backstage-goalie
bot
changed the title
backstage-service
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
da19170 to
0ef40b8
Compare
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
0ef40b8 to
6313241
Compare
backstage-service
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
6313241 to
b176093
Compare
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
b176093 to
49923d9
Compare
backstage-service
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
49923d9 to
2208b4c
Compare
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
2208b4c to
5ef7336
Compare
backstage-service
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
5ef7336 to
368e6e3
Compare
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
368e6e3 to
fa5956b
Compare
backstage-service
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
fa5956b to
97407db
Compare
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
97407db to
890d905
Compare
backstage-goalie
bot
changed the title
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
15 times, most recently
from
9382f53 to
cdbd380
Compare
Signed-off-by: Renovate Bot <[email protected]>
backstage-goalie
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
cdbd380 to
09f1e1b
Compare
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:
4.1.0->4.1.13.14.1->3.14.2js-yaml has prototype pollution in merge (<<)
CVE-2025-64718 / GHSA-mh29-5h37-fv8m
More information
Details
Impact
In js-yaml 4.1.0, 4.0.0, and 3.14.1 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (
__proto__). All users who parse untrusted yaml documents may be impacted.Patches
Problem is patched in js-yaml 4.1.1 and 3.14.2.
Workarounds
You can protect against this kind of attack on the server by using
node --disable-proto=deleteordeno(in Deno, pollution protection is on by default).References
https://cheatsheetseries.owasp.org/cheatsheets/Prototype_Pollution_Prevention_Cheat_Sheet.html
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
nodeca/js-yaml (js-yaml)
v4.1.1Compare Source
Security
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.