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

GitHub 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=delete or deno (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)

v4.1.1

Compare Source

Security

• Fix prototype pollution issue in yaml merge (<<) operator.

---

Configuration

📅 Schedule: Branch creation - "" (UTC), 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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	aws-sdk@​2.1692.0
	consul@​0.40.0
	@​types/​lodash.merge@​4.6.9
	@​types/​qs@​6.15.0 ⏵ 6.9.18
	@​types/​glob@​8.1.0
	@​typescript-eslint/​parser@​7.18.0
	callsite@​1.0.0
	@​types/​hapi__vision@​5.5.8
	@​types/​split2@​4.2.3
	@​types/​consul@​0.40.3
	@​types/​readable-stream@​4.0.18
	bluebird-retry@​0.11.0
	common-errors@​1.2.0
	@​types/​restify@​8.5.12
	@​types/​sinon@​17.0.3
	@​types/​get-value@​3.0.5
	@​typescript-eslint/​eslint-plugin@​7.18.0
	@​types/​lodash@​4.17.14
	aws4@​1.13.2
	@​types/​node@​22.10.10
	cross-env@​7.0.3
	readable-stream@​4.7.0
	execa@​8.0.1
	cheerio@​1.0.0
	c8@​10.1.3
	@​types/​debug@​4.1.12
	conventional-changelog-angular@​8.0.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm buffer is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: pnpm-lock.yaml → npm/aws-sdk@2.1692.0 → npm/buffer@4.9.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/buffer@4.9.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report