Repository navigation
fix(deps): update undici to v8 - #694
renovate[bot] wants to merge 2 commits into
Conversation
Bundle Stats✅ No significant changes. All scenario measurements (1)🗺️ View treemap · Artifacts
Significant means at least 1.0 KB and 1% gzip, or at least 5 ms and 10% import time. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 04c29d9. Configure here.
| }, | ||
| "dependencies": { | ||
| "undici": "^7.30.0" | ||
| "undici": "^8.11.2" |
There was a problem hiding this comment.
Undici v8 raises Node requirement
Medium Severity
undici v8 requires Node >=22.19.0, but this package still declares engines.node as >=22.12.0 and CI still tests 22.12.0. Consumers on 22.12–22.18 stay inside the advertised range and can hit install or runtime failures, and the 22.12.0 job can fail ls-engines.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 04c29d9. Configure here.
04c29d9 to
14abd07
Compare
2403ad4 to
7de97ec
Compare
d0f20d5 to
5650ebc
Compare
rexxars
left a comment
rexxars
left a comment
There was a problem hiding this comment.
Not compatible with our supported node versions. Needs to wait until we bump to 22.19, technically speaking.
106a93a to
1c7a292
Compare
d822f5d to
956942b
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
58a52fa to
14eba43
Compare
This branch has not been deployed
1 participant
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^7.30.0→^8.12.2^7.30.0→^8.12.2Release Notes
nodejs/undici (undici)
v8.12.2Compare Source
Security fixes
High severity
Denial of service via TLS 1.2 certificate-changing renegotiation
CVE-2026-87018 · GHSA-qrxm-fqhp-jwvm
A malicious or compromised HTTPS server could crash the Node.js process by initiating TLS 1.2 renegotiation and presenting a different, CA-trusted certificate whose hostname did not match the requested host. The resulting socket error reached an assertion in undici's HTTP/1.1 and HTTP/2 connection handling. This release handles post-connect certificate errors without terminating the process.
TLS certificate validation bypass through dropped
AgentoptionsCVE-2026-109383 · GHSA-2m5v-pch6-74hx
Agentused a JSON-based clone for constructor options, which silently removed function-valued TLS options such ascheckServerIdentity. Applications relying on custom certificate or public-key verification could therefore accept a certificate that the callback was intended to reject. This release preserves TLS options when creating per-origin dispatchers.Cache poisoning and cross-user disclosure through cross-origin redirects
CVE-2026-109829 · GHSA-4w7w-5xrc-9h26
When an originless
Agentcombined redirect and shared-cache interceptors ascompose(redirect(), cache()), a response from a cross-origin redirect could be stored under the original URL. This could allow persistent cache poisoning or disclosure of user-specific responses to later callers. This release verifies the response origin before caching and preserves redirect-hop cache-control policy.Denial of service through excessive
Content-EncodingvaluesCVE-2026-109869 · GHSA-xjj6-f33q-929c
A malicious HTTP server could crash the Node.js process by returning more than five content codings and closing the connection before sending the body. Although
fetch()rejected the response, an error from an orphaned internal stream could remain unhandled. This release validates the content-encoding chain before creating the body stream and aborts oversized chains safely.Medium severity
Denial of service through the
decompressinterceptorCVE-2026-87029 · GHSA-55wc-3pg8-jfw6
An exception thrown by a downstream response handler from an asynchronous decompression callback could escape as an uncaught exception. A server could trigger this when
decompresswas composed with a handler such asdumpwith a size limit. This release converts downstream handler exceptions into per-request errors.Subresource Integrity bypass with non-lowercase algorithm tokens
CVE-2026-109841 · GHSA-f72v-6w45-q472
fetch()treated valid mixed-case or uppercase SRI algorithm tokens, such asSHA256, as unknown and could accept a response whose body did not match the configured digest. This release normalizes algorithm tokens before validation and digest selection.Denial of service through unbounded EventSource parser state
CVE-2026-109924 · GHSA-4qv8-2p9j-2685
A malicious Server-Sent Events endpoint could exhaust process memory by sending many tiny
data:fields without completing an event, or by splitting an unfinished line across many chunks. This release bounds retained EventSource parser state, including field counts, buffered chunks, unfinished-line length, and retained field data.Denial of service through unbounded automatic WebSocket PONG buffering
CVE-2026-109932 · GHSA-9fm3-97px-rjf6
A malicious WebSocket server could exhaust process memory by flooding the client with PING frames while not reading the automatic PONG responses. undici previously ignored socket backpressure and allowed the outbound queue to grow without bound. This release pauses frame parsing when PONG writes encounter backpressure and resumes after the socket drains.
Full Changelog: nodejs/undici@v8.12.1...v8.12.2
v8.12.1Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v8.12.0...v8.12.1
v8.12.0Compare Source
What's Changed
.md->.htmlby @avivkeller in #5602New Contributors
Full Changelog: nodejs/undici@v8.11.2...v8.12.0
v8.11.2Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v8.11.1...v8.11.2
v8.11.1Compare Source
What's Changed
Full Changelog: nodejs/undici@v8.11.0...v8.11.1
v8.11.0Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v8.10.2...v8.11.0
v8.10.2Compare Source
High severity
BalancedPoolcould drop function-valued connection options while cloning its configuration, including custom TLS certificate validation callbacks. Undici now preservesconnectand legacytlsoptions when creating upstreams. Fixed by 8f5868fb.TypeErrorthat could terminate the process. Undici now rejects the handshake with protocol error 1002. Fixed by 66e12816.Medium severity
WebSocketStreamclose could create an unobserved rejected promise when its writable stream was locked, potentially terminating the process. Undici now propagates the failure through the retained writable stream controller. Fixed by 662d0ea6.Set-Cookie, disclosing one user's cookies to another caller. Undici now excludes these responses from shared caches, including existing entries and revalidation paths. Fixed by cb75bbb3.maxSize. Fixed by 7aac7f12.Low severity
POSTorDELETE. Undici now restricts cache reads and writes to safe methods while preserving invalidation by successful unsafe requests. Fixed by 2be07bf9.Content-Lengthwas present. Undici now enforcesmaxSizeagainst received bytes and aborts oversized responses. Fixed by 6d583124.Content-Rangeagainst the original response framing before resuming. Fixed by 0160a719.What's Changed
New Contributors
Full Changelog: nodejs/undici@v8.10.1...v8.10.2
v8.10.1Compare Source
What's Changed
New Contributors
Full Changelog: nodejs/undici@v8.10.0...v8.10.1
v8.10.0Compare Source
What's Changed
New Contributors
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate using a curated preset maintained by