Skip to content
VulniPulse
Medium5.9Red Hat Linux

Medium [CVE-2026-47221] Null pointer deref in internal redirects

This medium-severity Red Hat Linux advisory covers CVE-2026-47221 affecting Red Hat OpenShift Service Mesh 3.0, Red Hat OpenShift Service Mesh 3.1, Red Hat OpenShift Service Mesh 3.2.

CVE-2026-47221 Published Jun 26, 2026Updated by vendor Jun 26, 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

Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.18.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, the router filter contains a null pointer dereference vulnerability when handling HTTP 303 (See Other) internal redirects for body-less non-GET/HEAD requests.

When a POST, PUT, DELETE, or PATCH request without a body is sent to a route configured with internal redirect policy that includes 303 in redirect_response_codes, and the upstream responds with HTTP 303, the redirect handling code attempts to drain a request body buffer that was never allocated.

This results in a segmentation fault that crashes the entire Envoy process. When route configured with internal_redirect_policy including 303 in redirect_response_codes and upstream must return HTTP 303 response, an unauthenticated attacker can exploit this to cause complete denial of service, terminating all active connections.

This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3. A flaw was found in Envoy.

Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-476.

Affected Red Hat products: Red Hat OpenShift Service Mesh 3.0; Red Hat OpenShift Service Mesh 3.1; Red Hat OpenShift Service Mesh 3.2; Red Hat OpenShift Service Mesh 3.3; OpenShift Service Mesh 2. Will not fix / out of support: OpenShift Service Mesh 2.

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 12 days ago·verify at source

Fixed versions
  • 1.35.13
  • 1.36.9
  • 1.37.5
  • 1.38.3
  • openshift-service-mesh/istio-proxyv2-rhel9:1784908682
  • openshift-service-mesh/istio-proxyv2-rhel9:1784953556
  • openshift-service-mesh/istio-proxyv2-rhel9:1784953743
  • openshift-service-mesh/istio-proxyv2-rhel9:1784908639
  • RHSA-2026:49705
  • RHSA-2026:49729
  • RHSA-2026:49744
  • RHSA-2026:49765

Official advisory · high-confidence parse· fetched 12 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 12 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.