fix(deps): update dependency undici to v6.21.2 [security] #165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



This PR contains the following updates:
6.19.2->6.21.2GitHub Vulnerability Alerts
CVE-2024-38372
Impact
Depending on network and process conditions of a
fetch()request,response.arrayBuffer()might include portion of memory from the Node.js process.Patches
This has been patched in v6.19.2.
Workarounds
There are no known workaround.
References
https://github.com/nodejs/undici/issues/3337
https://github.com/nodejs/undici/issues/3328
https://github.com/nodejs/undici/pull/3338
nodejs/undici@f979ec3
CVE-2025-22150
Impact
Undici
fetch()uses Math.random() to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known.If there is a mechanism in an app that sends multipart requests to an attacker-controlled website, they can use this to leak the necessary values. Therefore, An attacker can tamper with the requests going to the backend APIs if certain conditions are met.
Patches
This is fixed in 5.28.5; 6.21.1; 7.2.3.
Workarounds
Do not issue multipart requests to attacker controlled servers.
References
Use of Insufficiently Random Values in undici
CVE-2025-22150 / GHSA-c76h-2ccp-4975
More information
Details
Impact
Undici
fetch()uses Math.random() to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known.If there is a mechanism in an app that sends multipart requests to an attacker-controlled website, they can use this to leak the necessary values. Therefore, An attacker can tamper with the requests going to the backend APIs if certain conditions are met.
Patches
This is fixed in 5.28.5; 6.21.1; 7.2.3.
Workarounds
Do not issue multipart requests to attacker controlled servers.
References
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
undici Denial of Service attack via bad certificate data
CVE-2025-47279 / GHSA-cxrh-j4jr-qwg3
More information
Details
Impact
Applications that use undici to implement a webhook-like system are vulnerable. If the attacker set up a server with an invalid certificate, and they can force the application to call the webhook repeatedly, then they can cause a memory leak.
Patches
This has been patched in https://github.com/nodejs/undici/pull/4088.
Workarounds
If a webhook fails, avoid keep calling it repeatedly.
References
Reported as: https://github.com/nodejs/undici/issues/3895
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
nodejs/undici (undici)
v6.21.2Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v6.21.1...v6.21.2
v6.21.1Compare Source
Fixes CVE CVE-2025-22150 GHSA-c76h-2ccp-4975 (embargoed until 22-01-2025).
What's Changed
183f8e9to v6.x by @ggoodman in https://github.com/nodejs/undici/pull/3855Full Changelog: nodejs/undici@v6.21.0...v6.21.1
v6.21.0Compare Source
What's Changed
Full Changelog: nodejs/undici@v6.20.1...v6.21.0
v6.20.1Compare Source
What's Changed
BodyReadable.bytesby @github-actions in https://github.com/nodejs/undici/pull/3711Full Changelog: nodejs/undici@v6.20.0...v6.20.1
v6.20.0Compare Source
What's Changed
v6.xbranch) by @eXhumer in https://github.com/nodejs/undici/pull/3531Full Changelog: nodejs/undici@v6.19.8...v6.20.0
v6.19.8Compare Source
Full Changelog: nodejs/undici@v6.19.7...v6.19.8
v6.19.7Compare Source
Full Changelog: nodejs/undici@v6.19.6...v6.19.7
v6.19.6Compare Source
Full Changelog: nodejs/undici@v6.19.5...v6.19.6
v6.19.5Compare Source
Full Changelog: nodejs/undici@v6.19.4...v6.19.5
v6.19.4Compare Source
Full Changelog: nodejs/undici@v6.19.3...v6.19.4
v6.19.3Compare Source
Full Changelog: nodejs/undici@v6.19.2...v6.19.3
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.