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% ✓ 398      ✗ 0   
     data_received..................: 93 MB   387 kB/s
     data_sent......................: 127 kB  526 B/s
     http_req_blocked...............: avg=82.77µs  min=2.13µs   med=3.97µs   max=2.38ms   p(90)=187.16µs p(95)=326.87µs
     http_req_connecting............: avg=65.07µs  min=0s       med=0s       max=2.33ms   p(90)=104.32µs p(95)=167.14µs
     http_req_duration..............: avg=115.01ms min=15.59ms  med=71.68ms  max=695.48ms p(90)=270.65ms p(95)=349.95ms
       { expected_response:true }...: avg=115.01ms min=15.59ms  med=71.68ms  max=695.48ms p(90)=270.65ms p(95)=349.95ms
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 398 
     http_req_receiving.............: avg=148.29µs min=58.08µs  med=121.64µs max=1.02ms   p(90)=215.13µs p(95)=298.35µs
     http_req_sending...............: avg=19.76µs  min=6.47µs   med=16.28µs  max=103.73µs p(90)=33.2µs   p(95)=43.3µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=114.84ms min=15.51ms  med=71.5ms   max=694.83ms p(90)=270.27ms p(95)=349.74ms
     http_reqs......................: 398     1.655406/s
     iteration_duration.............: avg=607.7ms  min=155.28ms med=658.1ms  max=1.21s    p(90)=859.85ms p(95)=903ms   
     iterations.....................: 76      0.316108/s
     vus............................: 0       min=0      max=4 
     vus_max........................: 60      min=60     max=60

Footnotes

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