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% ✓ 408      ✗ 0   
     data_received..................: 94 MB   390 kB/s
     data_sent......................: 53 kB   221 B/s
     http_req_blocked...............: avg=39.34µs  min=2.52µs   med=5.07µs   max=1.46ms p(90)=148.11µs p(95)=167.59µs
     http_req_connecting............: avg=25.38µs  min=0s       med=0s       max=1.41ms p(90)=97.66µs  p(95)=111.03µs
     http_req_duration..............: avg=154.71ms min=18.2ms   med=108.52ms max=1.09s  p(90)=349.04ms p(95)=424.63ms
       { expected_response:true }...: avg=154.71ms min=18.2ms   med=108.52ms max=1.09s  p(90)=349.04ms p(95)=424.63ms
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 408 
     http_req_receiving.............: avg=170.66µs min=43.63µs  med=146.5µs  max=1.1ms  p(90)=261µs    p(95)=327.04µs
     http_req_sending...............: avg=30.44µs  min=7.8µs    med=22.82µs  max=2.4ms  p(90)=38.61µs  p(95)=44.94µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s     p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=154.51ms min=18ms     med=108.38ms max=1.09s  p(90)=348.76ms p(95)=424.36ms
     http_reqs......................: 408     1.694076/s
     iteration_duration.............: avg=837.27ms min=284.58ms med=907.66ms max=1.89s  p(90)=1.16s    p(95)=1.34s   
     iterations.....................: 76      0.315563/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 ↩