Skip to content

chore(deps): update dependency js-yaml to v4.1.1 [security]#64

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-js-yaml-vulnerability
Open

chore(deps): update dependency js-yaml to v4.1.1 [security]#64
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-js-yaml-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 14, 2025

This PR contains the following updates:

Package Change Age Confidence
js-yaml 4.1.04.1.1 age confidence

js-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=delete or deno (in Deno, pollution protection is on by default).

References

https://cheatsheetseries.owasp.org/cheatsheets/Prototype_Pollution_Prevention_Cheat_Sheet.html

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

nodeca/js-yaml (js-yaml)

v4.1.1

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependency Includes dependency fixes label Nov 14, 2025
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from cf8d661 to 96f948c Compare November 18, 2025 23:48
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 96f948c to d4f80fd Compare December 3, 2025 17:51
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from d4f80fd to 8689729 Compare December 31, 2025 13:31
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from 085765c to e00d94f Compare January 23, 2026 19:13
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from e00d94f to 1277d31 Compare February 2, 2026 21:44
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 1277d31 to a687372 Compare February 12, 2026 13:36
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from a687372 to 6cb131b Compare March 5, 2026 20:52
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 6cb131b to 25464cd Compare March 13, 2026 12:09
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.1.1 [security] chore(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/npm-js-yaml-vulnerability branch March 27, 2026 01:07
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed chore(deps): update dependency js-yaml to v4.1.1 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from 25464cd to 0737242 Compare March 30, 2026 17:49
@renovate renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 0737242 to 5509cf9 Compare April 8, 2026 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependency Includes dependency fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants