CVE-2026-84947
undici vulnerable to response truncation via oversized chunked responses in the dump interceptor
undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
3.7
undici vulnerable to response truncation via oversized chunked responses in the dump interceptor
undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
- Record
CVE-2026-84947- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-20, CWE-248
- Updated
- 2026-11-02
EUVDEUVD-2026-71517
3.7
undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
- Record
EUVD-2026-71517- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-2gqq-gqf2-x968
3.7
undici vulnerable to response truncation via oversized chunked responses in the dump interceptor
Impact
undici's interceptors.dump() reads and discards response bodies up to a configurable maxSize. When a response declares a Content-Length that exceeds maxSize, the request is aborted cleanly. When a response is sent chunked (no Content-Length) and its body exceeds maxSize, it is not aborted: the interceptor ends the response early once the accumulated size reaches maxSize, and continued delivery from the parser triggers an internal assertion that is caught and turned into a request abort and connection tear-down. The application observes a misleading 200 with an empty or truncated body while the connection is disconnected. Any application using the dump interceptor against untrusted or misbehaving upstreams is affected.
Patches
Upgrade to 7.29.1 or 8.10.2. The dump interceptor now enforces maxSize on both the declared and the received body size, aborting the request with a RequestAbortedError instead of returning a truncated response.
Workarounds
None. Avoid using interceptors.dump() with untrusted upstreams until upgraded.
- Record
GHSA-2gqq-gqf2-x968- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-20, CWE-248
- Updated
- 2026-11-02
NVD
3.7
undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
- Record
CVE-2026-84947- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-20, CWE-248
- Updated
- 2026-11-02
OSV
3.7
undici vulnerable to response truncation via oversized chunked responses in the dump interceptor
undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
- Record
CVE-2026-84947- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-20, CWE-248
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-84947
5.3
undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
- Record
DEBIAN-CVE-2026-84947- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
Show 12 moreShow less
OSVGHSA-2gqq-gqf2-x968
3.7
undici vulnerable to response truncation via oversized chunked responses in the dump interceptor
Impact
undici's interceptors.dump() reads and discards response bodies up to a configurable maxSize. When a response declares a Content-Length that exceeds maxSize, the request is aborted cleanly. When a response is sent chunked (no Content-Length) and its body exceeds maxSize, it is not aborted: the interceptor ends the response early once the accumulated size reaches maxSize, and continued delivery from the parser triggers an internal assertion that is caught and turned into a request abort and connection tear-down. The application observes a misleading 200 with an empty or truncated body while the connection is disconnected. Any application using the dump interceptor against untrusted or misbehaving upstreams is affected.
Patches
Upgrade to 7.29.1 or 8.10.2. The dump interceptor now enforces maxSize on both the declared and the received body size, aborting the request with a RequestAbortedError instead of returning a truncated response.
Workarounds
None. Avoid using interceptors.dump() with untrusted upstreams until upgraded.
- Record
GHSA-2gqq-gqf2-x968- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-20, CWE-248
- Updated
- 2026-11-02
OSVRHSA-2026:54389
7.5
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- Record
RHSA-2026:54389- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:54438
7.4
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:54438- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:66008
8.8
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:66008- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-84947
3.7
undici's dump interceptor reads and discards a response body up to a configurable maximum size. When a response declares a Content-Length that exceeds the maximum, the interceptor aborts cleanly, but when a response has no Content-Length and is chunked, the interceptor instead signals completion early once the accumulated size reaches the maximum, without pausing or aborting the request. Because the underlying parser keeps delivering body bytes, a second completion signal fires and trips an internal assertion, which aborts the request and tears down the connection. The application is left observing a misleading successful status with an empty or truncated body while the connection has actually been disconnected. This affects undici versions from 7.1.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
- Record
UBUNTU-CVE-2026-84947- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
OSVCLSA-2026-1790719646 No score
TuxCare security update for undici (7 CVEs)
TuxCare rebuilt undici to address 7 CVEs. Fixed in 7.29.0-tuxcare.2.
- Record
CLSA-2026-1790719646- Updated
- 2026-11-02
OSVCLSA-2026-1790756064 No score
TuxCare security update for undici (6 CVEs)
TuxCare rebuilt undici to address 6 CVEs. Fixed in 7.28.0-tuxcare.3.
- Record
CLSA-2026-1790756064- Updated
- 2026-11-02
OSVCLSA-2026-1792478858 No score
TuxCare security update for undici (15 CVEs)
TuxCare rebuilt undici to address 15 CVEs. Fixed in 7.24.4-tuxcare.2.
- Record
CLSA-2026-1792478858- Updated
- 2026-11-05
OSVCLSA-2026-1792867308 No score
TuxCare security update for undici-types (7 CVEs)
TuxCare rebuilt undici-types to address 7 CVEs. Fixed in 7.29.0-tuxcare.2.
- Record
CLSA-2026-1792867308- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11884-1 No score
pi-coding-agent-0.87.1-1.1 on GA media
These are all security issues fixed in the pi-coding-agent-0.87.1-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11884-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:22111-1 No score
Security update for pi-coding-agent
This update for pi-coding-agent fixes the following issues:
Changes in pi-coding-agent:
-
Update to version 1.0.4 (1.0.3 was superseded the same day and never submitted):
- BREAKING: provider azure-openai-responses renamed to azure, now also serving Azure Foundry Chat Completions (azure/deepseek-v4-pro first). Rename the provider key in auth.json (or run /login again), models.json and settings.json (defaultProvider, enabledModels and modelThinkingLevels); sessions on the old provider fall back and lose prompt cache. AZURE_OPENAI_* env vars unchanged
- --tools and --exclude-tools take *-patterns and --no-mcp disables MCP for one run; --tools keeps MCP tools unless an entry starts with mcp__
- Codemode read() on image files yields an image block image() shows, and image() also saves each image to a temp file for later turns
- Fix fenced-code highlighting past the first line, MCP OAuth native-client registration, MCP shutdown racing a connecting server, Bedrock stalled-stream retries and frozen codemode built-ins, plus ChatGPT-login, EIO-on-closed-terminal and output-file-permission fixes
- Many more fixes and improvements; see upstream's release notes for the full list
-
Refresh the vendored node_modules 1.0.2 -> 1.0.4: the ten @earendil-works packages move to 1.0.4; nanoid, postcss and vite move too but are dev-only and not shipped. Still 119 shipped modules and the licence union is unchanged
- CVE-2026-102276 (boo#1283188): brace-expansion is 5.0.12, above the 5.0.10 fix floor, so the package is not affected by it
- CVE-2026-102277 (boo#1283392) and CVE-2026-102278 (boo#1283412): brace-expansion is 5.0.12, at the 5.0.12 and above the 5.0.11 fix floors, so the package is not affected by them
-
Update to version 1.0.2: patch releases on the 1.0 API, with no breaking changes
- models.json takes samplingParamsByThinkingLevel next to the existing samplingParams, so an OpenAI-compatible model can set temperature, top_p and the like separately for off, minimal, low, medium, high, xhigh and max. Model defaults, the effective level's override and the request are merged per key, modelOverrides merges per level, and the levels are pi's own, not the provider's thinkingLevelMap values. Only openai-completions, openai-responses and azure-openai-responses apply them
- MCP servers can be enabled, disabled or re-scoped per project from a .pi/mcp.json entry without a command or url, and /mcp toggles a user-level server for the current project
- oauth.clientRegistration: "cimd" identifies pi by its Client ID Metadata Document instead of dynamic client registration
- pi.registerToolRenderer() picks how calls to a tool that is not registered yet are drawn, such as MCP tools in a resumed session
- Cloudflare's Clef and Clef Flash classifier models are usable from codemode scripts and extensions
- A codemode script printing in a loop now fails at 16 Mi characters or 100000 items instead of running pi out of memory
- MCP tool calls in resumed sessions and HTML exports no longer render fully expanded until their server connects
- JPEG, GIF and WebP images that extensions draw through Image now appear in Kitty, Ghostty, WezTerm and Warp, and fullscreen Kitty images no longer collapse to a one-row strip after scrolling in WezTerm
- Many more fixes and improvements; see upstream's release notes for the full list
-
Refresh the vendored node_modules over 1.0.0 -> 1.0.2: the ten @earendil-works packages move to 1.0.2, with pi-telemetry the one that was already at 1.0.2 in the 1.0.1 tree, plus @anthropic-ai/sdk to 0.129.0. No module leaves or joins the 119 shipped ones and the licence union is unchanged
- CVE-2026-102276 (boo#1283188): brace-expansion is 5.0.12, above the 5.0.10 fix floor, so the package is not affected by it. Upstream's 1.0.1 made…
- Record
openSUSE-SU-2026:22111-1- Updated
- 2026-11-02
OSVROOT-APP-NPM-CVE-2026-84947 No score
CVE-2026-84947 in undici - Patched by Root
Root has patched CVE-2026-84947 in the undici package for Root:npm. Multiple fixed versions available.
- Record
ROOT-APP-NPM-CVE-2026-84947- Updated
- 2026-11-06
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
undicinpm |
7.1.0 up to 7.29.1 | 7.29.1 |
undicinpm |
8.0.0 up to 8.10.2 | 8.10.2 |
undiciTuxCare:npm From an advisory covering 7 CVEs |
7.29.0-tuxcare.0 up to 7.29.0-tuxcare.2, plus listed versions 7.29.07.29.0-tuxcare.1 |
7.29.0-tuxcare.2 |
undiciTuxCare:npm From an advisory covering 6 CVEs |
7.28.0-tuxcare.0 up to 7.28.0-tuxcare.3, plus listed versions 7.28.07.28.0-tuxcare.17.28.0-tuxcare.2 |
7.28.0-tuxcare.3 |
undiciTuxCare:npm From an advisory covering 13 CVEs |
7.24.4-tuxcare.0 up to 7.24.4-tuxcare.2, plus listed versions 7.24.47.24.4-tuxcare.1 |
7.24.4-tuxcare.2 |
undici-typesTuxCare:npm From an advisory covering 7 CVEs |
7.29.0-tuxcare.0 up to 7.29.0-tuxcare.2, plus listed versions 7.29.07.29.0-tuxcare.1 |
7.29.0-tuxcare.2 |
node-undiciDebian:12 |
All versions, plus listed versions 5.15.0+dfsg1+~cs20.10.9.3-15.15.0+dfsg1+~cs20.10.9.3-1+deb12u15.15.0+dfsg1+~cs20.10.9.3-1+deb12u25.15.0+dfsg1+~cs20.10.9.3-1+deb12u35.15.0+dfsg1+~cs20.10.9.3-1+deb12u4 Show 35 moreShow less5.19.1+dfsg1+~cs20.10.9.5-15.19.1+dfsg1+~cs20.10.9.5-25.22.1+dfsg1+~cs20.10.10.2-15.26.3+dfsg1+~cs23.10.12-15.26.3+dfsg1+~cs23.10.12-25.26.3+dfsg1+~cs23.10.12-35.28.0+dfsg1+~cs23.11.12.3-15.28.0+dfsg1+~cs23.11.12.3-25.28.2+dfsg1+~cs23.11.12.3-15.28.2+dfsg1+~cs23.11.12.3-25.28.2+dfsg1+~cs23.11.12.3-35.28.2+dfsg1+~cs23.11.12.3-45.28.2+dfsg1+~cs23.11.12.3-55.28.2+dfsg1+~cs23.11.12.3-65.28.4+dfsg1+~cs23.12.11-15.28.4+dfsg1+~cs23.12.11-27.1.0+dfsg1+~cs24.12.10-17.15.0+dfsg+~cs3.2.0-17.15.0+dfsg+~cs3.2.0-37.16.0+dfsg+~cs3.2.0-17.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-17.2.3+dfsg1+~cs24.12.11-17.2.3+dfsg1+~cs24.12.11-27.24.5+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-27.24.6+dfsg+~cs3.2.0-37.3.0+dfsg1+~cs24.12.11-17.3.0+dfsg1+~cs24.12.11-28.10.2+dfsg+~cs3.2.2-18.5.0+dfsg+~cs3.2.0-18.5.0+dfsg+~cs3.2.0-28.5.0+dfsg+~cs3.2.0-38.9.0+dfsg+~cs3.2.0-1 |
None known |
node-undiciDebian:13 |
All versions, plus listed versions 7.15.0+dfsg+~cs3.2.0-17.15.0+dfsg+~cs3.2.0-37.16.0+dfsg+~cs3.2.0-17.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-1 Show 11 moreShow less7.24.5+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-27.24.6+dfsg+~cs3.2.0-37.3.0+dfsg1+~cs24.12.11-17.3.0+dfsg1+~cs24.12.11-28.10.2+dfsg+~cs3.2.2-18.5.0+dfsg+~cs3.2.0-18.5.0+dfsg+~cs3.2.0-28.5.0+dfsg+~cs3.2.0-38.9.0+dfsg+~cs3.2.0-1 |
None known |
node-undiciDebian:14 |
before 8.10.2+dfsg+~cs3.2.2-1, plus listed versions 7.15.0+dfsg+~cs3.2.0-17.15.0+dfsg+~cs3.2.0-37.16.0+dfsg+~cs3.2.0-17.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-1 Show 10 moreShow less7.24.5+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-27.24.6+dfsg+~cs3.2.0-37.3.0+dfsg1+~cs24.12.11-17.3.0+dfsg1+~cs24.12.11-28.5.0+dfsg+~cs3.2.0-18.5.0+dfsg+~cs3.2.0-28.5.0+dfsg+~cs3.2.0-38.9.0+dfsg+~cs3.2.0-1 |
8.10.2+dfsg+~cs3.2.2-1 |
nodejs26Red Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:26.7.0-1.5.2.hum1 | 0:26.7.0-1.5.2.hum1 |
Show 24 moreShow less
| Package | Affected | Fixed |
|---|---|---|
nodejs26-binRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:26.7.0-1.5.2.hum1 | 0:26.7.0-1.5.2.hum1 |
nodejs26-develRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:26.7.0-1.5.2.hum1 | 0:26.7.0-1.5.2.hum1 |
nodejs26-docsRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:26.7.0-1.5.2.hum1 | 0:26.7.0-1.5.2.hum1 |
nodejs26-full-i18nRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:26.7.0-1.5.2.hum1 | 0:26.7.0-1.5.2.hum1 |
nodejs26-libsRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:26.7.0-1.5.2.hum1 | 0:26.7.0-1.5.2.hum1 |
nodejs26-npmRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:11.19.0-1.26.7.0.1.5.2.hum1 | 0:11.19.0-1.26.7.0.1.5.2.hum1 |
nodejs26-npm-binRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:26.7.0-1.5.2.hum1 | 0:26.7.0-1.5.2.hum1 |
v8-14.6-develRed Hat:hummingbird:1 From an advisory covering 10 CVEs |
before 0:14.6.202.34-1.26.7.0.1.5.2.hum1 | 0:14.6.202.34-1.26.7.0.1.5.2.hum1 |
nodejs24Red Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:24.18.1-0.2.2.hum1 | 0:24.18.1-0.2.2.hum1 |
nodejs24-binRed Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:24.18.1-0.2.2.hum1 | 0:24.18.1-0.2.2.hum1 |
nodejs24-develRed Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:24.18.1-0.2.2.hum1 | 0:24.18.1-0.2.2.hum1 |
nodejs24-docsRed Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:24.18.1-0.2.2.hum1 | 0:24.18.1-0.2.2.hum1 |
nodejs24-full-i18nRed Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:24.18.1-0.2.2.hum1 | 0:24.18.1-0.2.2.hum1 |
nodejs24-libsRed Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:24.18.1-0.2.2.hum1 | 0:24.18.1-0.2.2.hum1 |
nodejs24-npmRed Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:11.16.0-1.24.18.1.0.2.2.hum1 | 0:11.16.0-1.24.18.1.0.2.2.hum1 |
nodejs24-npm-binRed Hat:hummingbird:1 From an advisory covering 9 CVEs |
before 0:24.18.1-0.2.2.hum1 | 0:24.18.1-0.2.2.hum1 |
grafana12.4Red Hat:hummingbird:1 From an advisory covering 12 CVEs |
before 0:12.4.10-0.2.hum1 | 0:12.4.10-0.2.hum1 |
undiciRoot:npm |
before 8.10.2-aikido.1 | 8.10.2-aikido.18.10.2-aikido.28.10.2-aikido.37.29.1-aikido.17.29.1-aikido.28.10.2-aikido.4 |
@rootio/undiciRoot:npm |
before 8.10.2-root.io.1 | 8.10.2-root.io.18.10.2-root.io.28.10.2-root.io.37.29.1-root.io.17.29.1-root.io.28.10.2-root.io.4 |
node-undiciUbuntu:24.04:LTS |
All versions, plus listed versions 5.22.1+dfsg1+~cs20.10.10.2-1ubuntu15.26.3+dfsg1+~cs23.10.12-2 |
None known |
node-undiciUbuntu:26.10 |
All versions, plus listed versions 7.18.2+dfsg+~cs3.2.0-1build17.24.6+dfsg+~cs3.2.0-38.5.0+dfsg+~cs3.2.0-28.5.0+dfsg+~cs3.2.0-38.9.0+dfsg+~cs3.2.0-1 |
None known |
node-undiciUbuntu:26.04:LTS |
All versions, plus listed versions 7.3.0+dfsg1+~cs24.12.11-27.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-17.18.2+dfsg+~cs3.2.0-1build1 |
None known |
pi-coding-agentopenSUSE:Tumbleweed From an advisory covering 3 CVEs |
before 0.87.1-1.1 | 0.87.1-1.1 |
pi-coding-agentopenSUSE:Leap 16.0 From an advisory covering 11 CVEs |
before 1.0.4-bp160.1.1 | 1.0.4-bp160.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | ||
| affected | OSV | |
| facts | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-84947 is a low vulnerability (CVSS 3.7) in Nodejs Undici, published August 13, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.20%, the 9th percentile. Fixed in undici 7.29.1.
References
github.com/nodejs/undici/security/advisories/GHSA-2gqq-gqf2-x968
cna.openjsf.org/security-advisories.html
nvd.nist.gov/vuln/detail/CVE-2026-84947
github.com/nodejs/undici/commit/21693f406f0142f3504192e9f9b022dcf84782ae
github.com/nodejs/undici/commit/6d583124e7cf60b640097d64144ed633cc450584
github.com/nodejs/undici/releases/tag/v7.29.1
Show 113 moreShow less
github.com/nodejs/undici/releases/tag/v8.10.2
github.com/advisories/GHSA-2gqq-gqf2-x968
github.com/CVEProject/cvelistV5/tree/main/cves/2026/84xxx/CVE-2026-84947.json
security-tracker.debian.org/tracker/CVE-2026-84947
github.com/nodejs/undici
access.redhat.com/errata/RHSA-2026:54389
access.redhat.com/security/cve/CVE-2026-14257
access.redhat.com/security/cve/CVE-2026-69152
access.redhat.com/security/updates/classification
images.redhat.com
access.redhat.com/security/cve/CVE-2026-84947
access.redhat.com/security/cve/CVE-2026-85152
access.redhat.com/security/cve/CVE-2026-84933
access.redhat.com/security/cve/CVE-2026-18149
access.redhat.com/security/cve/CVE-2026-84890
access.redhat.com/security/cve/CVE-2026-85014
access.redhat.com/security/cve/CVE-2026-85008
access.redhat.com/security/cve/CVE-2026-48932
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_54389.json
bugzilla.redhat.com/show_bug.cgi?id=2506433
cve.org/CVERecord?id=CVE-2026-14257
nvd.nist.gov/vuln/detail/CVE-2026-14257
github.com/juliangruber/brace-expansion
github.com/juliangruber/brace-expansion/commit/a1bd33999ea75262c4749fff3bbb0d1372bd07b5
npmjs.com/package/brace-expansion
bugzilla.redhat.com/show_bug.cgi?id=2528802
cve.org/CVERecord?id=CVE-2026-18149
nvd.nist.gov/vuln/detail/CVE-2026-18149
github.com/nodejs/undici/security/advisories/GHSA-pmjh-fq2x-6v4x
bugzilla.redhat.com/show_bug.cgi?id=2526627
cve.org/CVERecord?id=CVE-2026-48932
nvd.nist.gov/vuln/detail/CVE-2026-48932
hackerone.com/reports/3564941
bugzilla.redhat.com/show_bug.cgi?id=2510722
cve.org/CVERecord?id=CVE-2026-69152
nvd.nist.gov/vuln/detail/CVE-2026-69152
github.com/juliangruber/brace-expansion/commit/139d015104e71433ad52a41d19467c48ecbb2c7d
github.com/juliangruber/brace-expansion/commit/1e30c930238d7162802d88a94189182def178dac
github.com/juliangruber/brace-expansion/commit/688a99eeaab02627c2b89ba8ba4821fecfa659cf
github.com/juliangruber/brace-expansion/commit/cb4b9e47cc2ec777c14b2b4492fb431a56f6a031
github.com/juliangruber/brace-expansion/security/advisories/GHSA-rgw5-rvv9-x895
bugzilla.redhat.com/show_bug.cgi?id=2528772
cve.org/CVERecord?id=CVE-2026-84890
nvd.nist.gov/vuln/detail/CVE-2026-84890
github.com/nodejs/undici/security/advisories/GHSA-3xpg-4rpp-hhhm
bugzilla.redhat.com/show_bug.cgi?id=2528756
cve.org/CVERecord?id=CVE-2026-84933
nvd.nist.gov/vuln/detail/CVE-2026-84933
github.com/nodejs/undici/security/advisories/GHSA-2jfj-6hjv-fm6j
bugzilla.redhat.com/show_bug.cgi?id=2528754
cve.org/CVERecord?id=CVE-2026-84947
bugzilla.redhat.com/show_bug.cgi?id=2528747
cve.org/CVERecord?id=CVE-2026-85008
nvd.nist.gov/vuln/detail/CVE-2026-85008
github.com/nodejs/undici/security/advisories/GHSA-8436-99hf-9mmv
bugzilla.redhat.com/show_bug.cgi?id=2528712
cve.org/CVERecord?id=CVE-2026-85014
nvd.nist.gov/vuln/detail/CVE-2026-85014
github.com/nodejs/undici/security/advisories/GHSA-rx4f-c7p8-82vq
bugzilla.redhat.com/show_bug.cgi?id=2528717
cve.org/CVERecord?id=CVE-2026-85152
nvd.nist.gov/vuln/detail/CVE-2026-85152
github.com/nodejs/undici/security/advisories/GHSA-vp8m-p9jh-q5pm
access.redhat.com/errata/RHSA-2026:54438
access.redhat.com/security/cve/CVE-2026-84961
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_54438.json
bugzilla.redhat.com/show_bug.cgi?id=2528735
cve.org/CVERecord?id=CVE-2026-84961
nvd.nist.gov/vuln/detail/CVE-2026-84961
github.com/nodejs/undici/security/advisories/GHSA-w293-vg96-wgc3
access.redhat.com/errata/RHSA-2026:66008
access.redhat.com/security/cve/CVE-2026-19534
access.redhat.com/security/cve/CVE-2026-18540
access.redhat.com/security/cve/CVE-2026-14199
access.redhat.com/security/cve/CVE-2026-28378
access.redhat.com/security/cve/CVE-2026-19197
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_66008.json
bugzilla.redhat.com/show_bug.cgi?id=2521850
cve.org/CVERecord?id=CVE-2026-14199
nvd.nist.gov/vuln/detail/CVE-2026-14199
grafana.com/security/security-advisories/cve-2026-14199
bugzilla.redhat.com/show_bug.cgi?id=2528783
cve.org/CVERecord?id=CVE-2026-18540
nvd.nist.gov/vuln/detail/CVE-2026-18540
github.com/nodejs/undici/security/advisories/GHSA-r53p-7pc4-xj5r
bugzilla.redhat.com/show_bug.cgi?id=2524303
cve.org/CVERecord?id=CVE-2026-19197
nvd.nist.gov/vuln/detail/CVE-2026-19197
grafana.com/security/security-advisories/cve-2026-19197
bugzilla.redhat.com/show_bug.cgi?id=2528759
cve.org/CVERecord?id=CVE-2026-19534
nvd.nist.gov/vuln/detail/CVE-2026-19534
github.com/nodejs/undici/security/advisories/GHSA-rfgv-xxqx-mfg5
bugzilla.redhat.com/show_bug.cgi?id=2497887
cve.org/CVERecord?id=CVE-2026-28378
nvd.nist.gov/vuln/detail/CVE-2026-28378
grafana.com/security/security-advisories/cve-2026-28378
ubuntu.com/security/CVE-2026-84947
suse.com/security/cve/CVE-2026-84933
suse.com/security/cve/CVE-2026-84947
suse.com/security/cve/CVE-2026-84961
bugzilla.suse.com/1279832
bugzilla.suse.com/1283188
bugzilla.suse.com/1283392
bugzilla.suse.com/1283412
suse.com/security/cve/CVE-2026-102276
suse.com/security/cve/CVE-2026-102277
suse.com/security/cve/CVE-2026-102278
suse.com/security/cve/CVE-2026-84890
suse.com/security/cve/CVE-2026-85008
suse.com/security/cve/CVE-2026-85014
suse.com/security/cve/CVE-2026-85024
suse.com/security/cve/CVE-2026-85152
Left out here: the rest of 1 source description. The JSON record has them.