External risk intelligence

Undici Cache Interceptor Vulnerability Discloses Private Data and Causes Process Termination

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-13697

Undici is a low-level HTTP client library for Node.js used by many different applications. While it can be used in internet-facing web servers or proxies where cache interceptors might be exposed to external traffic, it is equally used in internal services, CLI tools, and backend background tasks where public exposure is not guaranteed.

Information Disclosure

Nodejs Undici

7.0.0 to before 7.29.08.0.0 to before 8.9.0

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in the undici library, a Node.js HTTP client, affecting its cache interceptor. This flaw could allow sensitive information, such as private response bodies and headers, to be inadvertently disclosed to unintended parties when improperly configured cache directives are used. In some cases, the issue could also cause applications to terminate unexpectedly.

  • Sensitive data exposure via cache.
  • Affects applications using undici's cache interceptor.
  • Confirm relevance and exposure to sensitive data.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted Cache-Control headers to an application using the undici HTTP client library's cache interceptor. If the application processes these headers, it may inadvertently store sensitive information or crash, depending on the exact malformation.

  • Exposed to network traffic.
  • Malformed Cache-Control header.
  • Data disclosure or process termination.

Live Threat

Current exploitation, exposure, and threat context

When the cache interceptor is used in shared mode, malformed `Cache-Control` private directives could lead to sensitive response data being stored in the cache and later served to unintended users. Additionally, specific malformed `Cache-Control` headers can cause the application to crash. Both behaviors depend on the application's configuration and error handling when using the cache interceptor.

  • Private response data could be exposed.
  • Malformed directives could cause cache poisoning.
  • Uncaught errors may terminate the process.

Operational Fix

Recommended remediation, mitigation, and detection steps

The `undici` library's cache interceptor is used in Node.js applications, so application owners and platform teams are likely responsible for addressing this vulnerability. The first step is to identify all instances where `undici` is utilized, confirm if the cache interceptor is enabled and accessible, and then plan remediation based on the criticality of affected services.

  • Application owners should own the issue.
  • Verify `undici` cache interceptor usage.
  • Plan remediation considering business impact.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the undici library used for in Node.js?

Undici is a low-level HTTP client library built for Node.js. Developers use it to manage network requests efficiently. It includes an optional cache interceptor feature, which is designed to store responses locally so that subsequent requests for the same resource can be served faster without re-fetching data from the network.

How does CVE-2026-13697 trigger data leaks or crashes?

This vulnerability involves Improper Information Neutralization (CWE-200) and Uncaught Exception (CWE-248). When the cache interceptor processes malformed 'Cache-Control' headers, it may incorrectly store private data—like session cookies—in a shared cache. Alternatively, specific header combinations cause a parsing error that, if not caught, can crash the entire application process.

When does this vulnerability NOT trigger?

The issues specifically impact applications that have the cache interceptor enabled in shared mode. If your application does not use the undici cache interceptor, or if it uses the library solely for outgoing requests that do not store or share cached responses, these specific risks regarding cache poisoning and process termination do not apply.

Is my application at risk based on Halo Surface Signal?

According to Halo Surface Signal, risk depends on how undici is deployed. While internet-facing servers or proxies using the cache interceptor are at higher risk of receiving malicious traffic, internal services, CLI tools, or background tasks using the library may have lower exposure. You should assess if your specific service processes external or untrusted 'Cache-Control' headers.

How should I respond to this threat?

Your first step is to audit your codebase to determine where undici is utilized and whether the cache interceptor is active. If enabled, prioritize updating undici to version 7.29.0 or 8.9.0, as these releases contain the necessary patches. Coordinate with your platform or development teams to verify these versions are deployed across all affected services.

References