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

[openverse-bot]

This PR contains the following updates:

Package	Type	Update	Change
js-yaml	dependencies	patch	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 - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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 has been generated by Renovate Bot.

[github-actions]

Latest k6 run output¹

     ✓ status was 200

     checks.........................: 100.00% ✓ 390      ✗ 0   
     data_received..................: 90 MB   373 kB/s
     data_sent......................: 124 kB  515 B/s
     http_req_blocked...............: avg=96.88µs  min=2.42µs   med=4.91µs   max=2.38ms   p(90)=186.56µs p(95)=651.15µs
     http_req_connecting............: avg=71.47µs  min=0s       med=0s       max=2.3ms    p(90)=134.53µs p(95)=432.15µs
     http_req_duration..............: avg=163.7ms  min=19.36ms  med=104.1ms  max=1s       p(90)=390.45ms p(95)=479.64ms
       { expected_response:true }...: avg=163.7ms  min=19.36ms  med=104.1ms  max=1s       p(90)=390.45ms p(95)=479.64ms
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 390 
     http_req_receiving.............: avg=192.92µs min=68.77µs  med=161.41µs max=2.33ms   p(90)=279.72µs p(95)=340.64µs
     http_req_sending...............: avg=28.2µs   min=8.43µs   med=25.21µs  max=157.21µs p(90)=47.75µs  p(95)=59.85µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=163.48ms min=19.22ms  med=103.94ms max=1s       p(90)=389.94ms p(95)=479.39ms
     http_reqs......................: 390     1.623413/s
     iteration_duration.............: avg=870.03ms min=205.57ms med=924.86ms max=1.85s    p(90)=1.2s     p(95)=1.28s   
     iterations.....................: 74      0.308032/s
     vus............................: 0       min=0      max=6 
     vus_max........................: 60      min=60     max=60

Footnotes

1. This comment will automatically update with new output each time k6 runs for this PR ↩