CVE-2026-2581: undici is vulnerable to Unbounded Memory Consumption in in Undici's DeduplicationHandler via Response Buffering leads to DoS

Published Mar 12, 2026
·
Updated

Impact This is an uncontrolled resource consumption vulnerability (CWE-400) that can lead to Denial of Service (DoS).

In vulnerable Undici versions, when interceptors.deduplicate() is enabled, response data for deduplicated requests could be accumulated in memory for downstream handlers. An attacker-controlled or untrusted upstream endpoint can exploit this with large/chunked responses and concurrent identical requests, causing high memory usage and potential OOM process termination.

Impacted users are applications that use Undici’s deduplication interceptor against endpoints that may produce large or long-lived response bodies.

Patches

The issue has been patched by changing deduplication behavior to stream response chunks to downstream handlers as they arrive (instead of full-body accumulation), and by preventing late deduplication when body streaming has already started.

Users should upgrade to the first official Undici (and Node.js, where applicable) releases that include this patch.

Workarounds If upgrading immediately is not possible:

- Disable interceptors.deduplicate() for affected clients/routes. - Use skipHeaderNames with a marker header to force high-risk requests to bypass deduplication. - Avoid concurrent identical requests to untrusted endpoints that may return very large/chunked bodies. - Apply upstream/proxy response-size and timeout limits.

Other sources

This is an uncontrolled resource consumption vulnerability (CWE-400) that can lead to Denial of Service (DoS).

In vulnerable Undici versions, when interceptors.deduplicate() is enabled, response data for deduplicated requests could be accumulated in memory for downstream handlers. An attacker-controlled or untrusted upstream endpoint can exploit this with large/chunked responses and concurrent identical requests, causing high memory usage and potential OOM process termination.

Impacted users are applications that use Undici’s deduplication interceptor against endpoints that may produce large or long-lived response bodies.

PatchesThe issue has been patched by changing deduplication behavior to stream response chunks to downstream handlers as they arrive (instead of full-body accumulation), and by preventing late deduplication when body streaming has already started.

Users should upgrade to the first official Undici (and Node.js, where applicable) releases that include this patch.

Red Hat

Affected Software

3 affected componentsFixes available
npm/undici
npm/undici>=7.17.0<7.24.0
7.24.0
Nodejs Undici Node.js>=7.17.0<7.24.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/undici to a version that resolves this vulnerability.

    Fixed in 7.24.0
  2. Configuration

    Disable `interceptors.deduplicate()` for affected clients/routes that call endpoints capable of returning large or long-lived response bodies.

    Undici (deduplication interceptor) interceptors.deduplicate() = disabled
  3. Configuration

    Use `skipHeaderNames` with a marker header so high-risk requests bypass deduplication and do not trigger response buffering behavior.

    Undici (deduplication interceptor) skipHeaderNames (with marker header) = configured to force high-risk requests to bypass deduplication
  4. Compensating control

    Apply upstream/proxy response-size and timeout limits to prevent attacker-controlled untrusted upstreams from returning very large or long-lived/chunked response bodies.

  5. Compensating control

    Avoid concurrent identical requests to untrusted endpoints that may return very large/chunked responses to reduce the chance of high memory usage in Undici deduplication.

Event History

Mar 12, 2026
CVE Published
via MITRE·08:13 PM
Data Sourced
via MITRE·08:13 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·09:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Mar 13, 2026
Advisory Published
via GitHub·08:37 PM
Data Sourced
via GitHub·08:37 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-2581?

CVE-2026-2581 is classified as a high severity vulnerability due to its potential to cause Denial of Service (DoS) through unbounded memory consumption.

2

How does CVE-2026-2581 affect applications using Undici?

CVE-2026-2581 can lead to uncontrolled resource consumption in applications using Undici, resulting in a Denial of Service condition.

3

Which versions of Undici are affected by CVE-2026-2581?

CVE-2026-2581 affects all vulnerable versions of Undici, specifically those with the deduplication handler issue.

4

How do I mitigate CVE-2026-2581?

To mitigate CVE-2026-2581, update to the latest version of Undici that addresses the unbounded memory consumption issue.

5

What is the main cause of CVE-2026-2581?

The main cause of CVE-2026-2581 is the unregulated response buffering in Undici's DeduplicationHandler.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203