chore(deps): update dependency js-yaml to v3.14.2 [security]#1237
chore(deps): update dependency js-yaml to v3.14.2 [security]#1237renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
size-limit report 📦
|
1e11e64 to
4e3a5fc
Compare
4e3a5fc to
5ec58e9
Compare
5ec58e9 to
457b1fc
Compare
457b1fc to
86e6b66
Compare
86e6b66 to
d00e5e7
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
d00e5e7 to
b258085
Compare
b258085 to
40736cd
Compare
40736cd to
5e463e4
Compare
5e463e4 to
4ccb06d
Compare
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 - "" (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 was generated by Mend Renovate. View the repository job log.