chore(deps): update dependency js-yaml to v4.1.1 [security] - #64
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency js-yaml to v4.1.1 [security]#64renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
November 18, 2025 23:48
cf8d661 to
96f948c
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
December 3, 2025 17:51
96f948c to
d4f80fd
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
December 31, 2025 13:31
d4f80fd to
8689729
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
2 times, most recently
from
January 23, 2026 19:13
085765c to
e00d94f
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
February 2, 2026 21:44
e00d94f to
1277d31
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
February 12, 2026 13:36
1277d31 to
a687372
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
March 5, 2026 20:52
a687372 to
6cb131b
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
March 13, 2026 12:09
6cb131b to
25464cd
Compare
renovate
Bot
changed the title
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
2 times, most recently
from
March 30, 2026 17:49
25464cd to
0737242
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
April 8, 2026 17:47
0737242 to
5509cf9
Compare
renovate
Bot
changed the title
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
2 times, most recently
from
April 27, 2026 21:49
5509cf9 to
fdcf7a6
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
May 12, 2026 11:07
fdcf7a6 to
66b9a16
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
May 28, 2026 17:13
66b9a16 to
ea27328
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
2 times, most recently
from
June 16, 2026 19:00
e89ee6d to
9cd5a23
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
June 29, 2026 21:13
9cd5a23 to
e312f63
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
2 times, most recently
from
July 16, 2026 17:25
04e647b to
51b2a91
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
2 times, most recently
from
July 24, 2026 15:05
131ed43 to
e839ac6
Compare
renovate
Bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
July 30, 2026 18:05
e839ac6 to
65b2129
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:
4.1.0→4.1.1js-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 the GitHub Advisory Database (CC-BY 4.0).
Release Notes
nodeca/js-yaml (js-yaml)
v4.1.1Compare Source
Security
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.