Skip to content

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

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

fix(deps): update dependency js-yaml to v4.1.1 [security]#645
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-js-yaml-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
js-yaml 4.1.04.1.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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 changed the title fix(deps): update dependency js-yaml to v4.1.1 [security] fix(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:43
@renovate renovate Bot changed the title fix(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed fix(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 e382c79 to 03a67dd Compare March 30, 2026 21:37
@renovate renovate Bot changed the title fix(deps): update dependency js-yaml to v4.1.1 [security] fix(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title fix(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed fix(deps): update dependency js-yaml to v4.1.1 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from 03a67dd to 3e41d97 Compare April 27, 2026 23:11
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 3e41d97 to 8af3445 Compare May 5, 2026 05:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants