CVE-2026-116592: Red Hat Cache poisoning via intermediate redirect hops
This Red Hat advisory covers CVE-2026-116592. Related products: Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Hardened Images.
- CVE-2026-116592
Key facts
- Vendor rating
- High, CVSS 7.4
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N· base score 7.4, scored by openjsAttack vector: network. Attack complexity: high. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: none.- Weakness
- CWE-346: Origin Validation Error
- CWE-524: Use of Cache Containing Sensitive Information
- EPSS
- 0.16% chance of exploitation in the next 30 days (4th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Versions named
- 7.30.1; 8.12.2; 8.12.3
- Fixed in
- nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1, RHSA-2026:99436
- Source published
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Related products & platforms
Description
Cache poisoning via intermediate redirect hops. Red Hat rates this important (CVSS 7.4).
Weakness: CWE-346. Red Hat lists fixing advisory RHSA-2026:99436 with package nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1.
Affected products named by the advisory: Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Hardened Images; Red Hat OpenShift AI (RHOAI); and 3 more.
Affected products named by the advisory: Red Hat OpenShift Container Platform 5; Red Hat OpenShift Virtualization 4; Red Hat Trusted Artifact Signer.
Text from the source record.
- 7.30.1
- 8.12.2
- 8.12.3
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-116592
Upgrade to a fixed release named by Red Hat:
- nodejs26-main-11.20.0-1.26.13.1.0.1.hum1
- nodejs26-main-26.13.1-0.1.hum1
- RHSA-2026:99436
Vendor guidance
- Configure Node.js applications utilizing undici to avoid vulnerable interceptor ordering: 1. Reorder interceptors: Structure the interceptor pipeline so caching is evaluated prior to redirection, such as using compose(cache(), redirect()). 2. Isolate cache boundaries: Replace shared originless Agent configurations with origin-bound Client or Pool dispatchers and separate cache stores. 3. Restrict shared caching: Disable shared caching on client requests that permit automated redirect following. Caveats: Disabling shared caching or modifying dispatcher architecture may increase request latency and backend server load. Warning: Applying these application configuration changes requires restarting the affected Node.js service. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to reconfigure undici interceptors to evaluate caching prior to redirection or isolate dispatchers and cache stores per origin: upgrade to undici 7.30.2, 8.12.4+ (or the corresponding fixed Red Hat builds), which account for intermediate redirect hops and enforce cache validation and header retention across all hops before storing responses under the original request key, closing all 3 injection vectors (intermediate redirect bounce through untrusted origin, dropping intermediate Vary header to expose private cached responses, laundering non-storable intermediate redirects via missing no-cache validation). Until patched, this is a concern on Node.js applications using an originless undici Agent composing redirect and shared cache interceptors, so reorder interceptors to evaluate cache before redirect, use origin-bound dispatchers with isolated cache stores, or disable shared caching on requests that permit redirect following. As a compensating measure, block outbound network connections to unapproved external endpoints to prevent reaching attacker-controlled intermediate redirect targets and restrict server-initiated requests and redirect hops to an explicit allowlist of permitted destinations. These controls limit blast radius and contain exploitation, but they do not fix the underlying intermediate redirect cache poisoning defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-208 Outbound Network Egress Restriction (SSRF Blast Radius Containment) (medium)
More Red Hat Linux advisories
CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli DecoderCVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-freeCVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCECVE-2026-48710May 26, 2026Security restriction bypass via malformed HTTP Host headerCVE-2026-125350Nov 10, 2026Use after free in XMLCVE-2026-114713Nov 8, 2026Command injection via unescaped message tag
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.