Skip to content
VulniPulse
Low3.7Red Hat Linux

Low [CVE-2026-6733] Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery.

This low-severity Red Hat Linux advisory covers CVE-2026-6733 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.

CVE-2026-6733 Published Jun 17, 2026Updated by vendor Jun 17, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes.

When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse.

Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool.

A flaw was found in undici. This could result in a low impact on data integrity.

This can lead to incorrect response delivery, potentially impacting data integrity, but requires a compromised server and active keep-alive connections. Red Hat severity: Low — CVSS 3.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).

Weakness: CWE-940.

Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Hardened Images; and 10 more.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Fixed versions
  • 26.0
  • 28.0
  • nodejs24-1:24.18.0-1.el10_2
  • nodejs22-1:22.23.1-2.el10_2
  • nodejs:24-8100020260630152626.6d880403
  • nodejs:22-8100020260703140402.6d880403
  • nodejs:24-9080020260626074955.rhel9
  • nodejs:22-9080020260626075442.rhel9
  • nodejs26-main-26.5.0-1.3.hum1
  • nodejs24-main-24.18.0-0.3.hum1
  • RHSA-2026:35841
  • RHSA-2026:35842
  • RHSA-2026:39868
  • RHSA-2026:41947
  • RHSA-2026:35891
  • RHSA-2026:35892
  • RHSA-2026:38009
  • RHSA-2026:38236

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Official advisory · high-confidence parse· fetched 15 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.