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% ✓ 410      ✗ 0   
     data_received..................: 96 MB   399 kB/s
     data_sent......................: 130 kB  541 B/s
     http_req_blocked...............: avg=83.66µs  min=2.33µs   med=4.72µs   max=2.19ms   p(90)=201.84µs p(95)=630.04µs
     http_req_connecting............: avg=45.42µs  min=0s       med=0s       max=2.07ms   p(90)=95.44µs  p(95)=169.27µs
     http_req_duration..............: avg=154.87ms min=14.79ms  med=106.03ms max=977.85ms p(90)=343.04ms p(95)=438.39ms
       { expected_response:true }...: avg=154.87ms min=14.79ms  med=106.03ms max=977.85ms p(90)=343.04ms p(95)=438.39ms
   ✓ http_req_failed................: 0.00%   ✓ 0        ✗ 410 
     http_req_receiving.............: avg=171.63µs min=59.92µs  med=147.13µs max=3.3ms    p(90)=246.96µs p(95)=298.77µs
     http_req_sending...............: avg=25.57µs  min=6.74µs   med=23.52µs  max=79.49µs  p(90)=43.41µs  p(95)=49.7µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=154.67ms min=14.67ms  med=105.8ms  max=977.55ms p(90)=342.81ms p(95)=438.08ms
     http_reqs......................: 410     1.702579/s
     iteration_duration.............: avg=831.52ms min=237.77ms med=877.6ms  max=1.66s    p(90)=1.16s    p(95)=1.21s   
     iterations.....................: 77      0.319753/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 ↩