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% ✓ 402      ✗ 0   
     data_received..................: 93 MB   388 kB/s
     data_sent......................: 53 kB   220 B/s
     http_req_blocked...............: avg=83.13µs  min=2.09µs   med=5.45µs   max=1.61ms   p(90)=181.48µs p(95)=692.27µs
     http_req_connecting............: avg=42.88µs  min=0s       med=0s       max=1.55ms   p(90)=102.12µs p(95)=164.6µs 
     http_req_duration..............: avg=142.78ms min=16.39ms  med=93.1ms   max=880.15ms p(90)=343.24ms p(95)=416.99ms
       { expected_response:true }...: avg=142.78ms min=16.39ms  med=93.1ms   max=880.15ms p(90)=343.24ms p(95)=416.99ms
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 402 
     http_req_receiving.............: avg=215.7µs  min=59.53µs  med=155.36µs max=5.35ms   p(90)=301.89µs p(95)=460.64µs
     http_req_sending...............: avg=25.29µs  min=10.11µs  med=20.94µs  max=119.81µs p(90)=37.38µs  p(95)=54.62µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=142.54ms min=16.25ms  med=92.68ms  max=879.82ms p(90)=343ms    p(95)=416.73ms
     http_reqs......................: 402     1.670001/s
     iteration_duration.............: avg=762.24ms min=230.66ms med=812.14ms max=1.59s    p(90)=1.06s    p(95)=1.07s   
     iterations.....................: 76      0.315722/s
     vus............................: 2       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 ↩