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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
js-yaml	4.1.0 → 4.1.1

---

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

• https://github.com/nodeca/js-yaml/security/advisories/GHSA-mh29-5h37-fv8m
• https://nvd.nist.gov/vuln/detail/CVE-2025-64718
• https://github.com/nodeca/js-yaml/commit/383665ff4248ec2192d1274e934462bb30426879
• https://github.com/nodeca/js-yaml/commit/5278870a17454fe8621dbd8c445c412529525266
• https://github.com/nodeca/js-yaml/issues/730#issuecomment-3549635876
• https://github.com/advisories/GHSA-mh29-5h37-fv8m

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

[cursor]

Stale comment

Found one high-severity issue that blocks treating this as a complete security fix:

• The lockfile still resolves reachable js-yaml@4.1.0 copies through other packages, so this branch does not fully remove the vulnerable version from the dependency graph. Running pnpm why js-yaml --recursive on this branch still reports js-yaml@4.1.0 via @eslint/eslintrc@3.3.1 and nx@14.4.3.

I did not find any other material issues in the changed hunk beyond that incomplete remediation risk.

  

_{Sent by Cursor Automation: Flatbread PR Review}

[cursor]

This updates one js-yaml edge to 4.1.1, but the lockfile still contains reachable js-yaml@4.1.0 entries elsewhere (@eslint/eslintrc@3.3.1 and nx@14.4.3 both still depend on it). pnpm why js-yaml --recursive on this branch still reports js-yaml@4.1.0, so the security remediation is incomplete and may leave the alert open. Please bump or re-resolve the packages that still pin 4.1.0 so every reachable js-yaml edge lands on 4.1.1+.

[cursor]

Stale comment

Review skipped — dependency-only update

This PR contains only a js-yaml version bump (security patch). The adversarial review DAG is not run for dependency-only updates.

  

_{Sent by Cursor Automation: Flatbread PR Review}

[cursor]

Flatbread Code-Review Orchestrator — skipped

This PR is a dependency-only update (Renovate bot: js-yaml → v4.1.1 security patch). The adversarial review DAG does not run for dependency-only changes.

  

_{Sent by Cursor Automation: Flatbread PR Review}