Skip to content

Update dependency js-yaml to v4.1.1 [SECURITY]#190

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

Update dependency js-yaml to v4.1.1 [SECURITY]#190
renovate[bot] wants to merge 1 commit intomasterfrom
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: 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.


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

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

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Nov 14, 2025

⚠️ No Changeset found

Latest commit: e7ee0a6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate Bot changed the title Update dependency js-yaml to v4.1.1 [SECURITY] 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:21
@renovate renovate Bot changed the title Update dependency js-yaml to v4.1.1 [SECURITY] - autoclosed 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 51efebd to 70491d9 Compare March 30, 2026 21:37
@renovate renovate Bot changed the title Update dependency js-yaml to v4.1.1 [SECURITY] 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 Update dependency js-yaml to v4.1.1 [SECURITY] - autoclosed 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 70491d9 to e7ee0a6 Compare April 27, 2026 22:48
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