Update dependency js-yaml to v3.14.2 [SECURITY] #625
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
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
02db084 to
3f931a6
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
3f931a6 to
ac1b2d2
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
ac1b2d2 to
8cf32b0
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
8cf32b0 to
e4ec6e0
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
e4ec6e0 to
7684d43
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
7684d43 to
e29ae37
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
e29ae37 to
d2fa956
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
d2fa956 to
8fc6609
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
8fc6609 to
be430de
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
be430de to
9ec16e6
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
9ec16e6 to
fa8862e
Compare
renovate
bot
force-pushed
the
renovate/npm-js-yaml-vulnerability
branch
from
fa8862e to
8653a4d
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:
3.14.1→3.14.2GitHub Vulnerability Alerts
CVE-2025-64718
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
Release Notes
nodeca/js-yaml (js-yaml)
v3.14.2Compare Source
Security
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - Between 02:00 PM and 06:59 PM, Monday through Thursday ( * 14-18 * * 1-4 ) in timezone Europe/London.
🚦 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.