CVE-2026-47221: Envoy: Null pointer deref in internal redirects

Published Jun 26, 2026
·
Updated

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 redirectresponsecodes, 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 internalredirectpolicy including 303 in redirectresponsecodes 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.

Affected Software

5 affected components
Envoy Envoy>1.18.0<=1.35.12, =1.36.9, =1.37.5, =1.38.3
Envoyproxy Envoy>=1.18.0<1.35.13
Envoyproxy Envoy>=1.36.0<1.36.9
Envoyproxy Envoy>=1.37.0<1.37.5
Envoyproxy Envoy>=1.38.0<1.38.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Envoy to a version that resolves this vulnerability.

    Fixed in 1.35.13
  2. Upgrade

    Upgrade Envoy to a version that resolves this vulnerability.

    Fixed in 1.36.9
  3. Upgrade

    Upgrade Envoy to a version that resolves this vulnerability.

    Fixed in 1.37.5
  4. Upgrade

    Upgrade Envoy to a version that resolves this vulnerability.

    Fixed in 1.38.3
  5. Configuration

    In routes using internal redirect policy, remove 303 (See Other) from internal_redirect_policy.redirect_response_codes to prevent the null pointer dereference during handling of HTTP 303 internal redirects for body-less non-GET/HEAD requests.

    Envoy router filter internal_redirect_policy.redirect_response_codes = Exclude 303

Event History

Jun 26, 2026
CVE Published
via MITRE·05:35 PM
Data Sourced
via MITRE·05:35 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 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-47221?

The severity of CVE-2026-47221 is classified as medium with a score of 5.9.

2

How do I fix CVE-2026-47221?

To fix CVE-2026-47221, upgrade to Envoy versions 1.35.14, 1.36.10, 1.37.6, or 1.38.4 or later.

3

What is the impact of CVE-2026-47221?

CVE-2026-47221 can lead to a null pointer dereference, causing potential application crashes during internal HTTP 303 redirects.

4

In which versions of Envoy is CVE-2026-47221 present?

CVE-2026-47221 is present in Envoy versions 1.18.0 through 1.35.13, 1.36.9, 1.37.5, and 1.38.3.

5

What types of requests are affected by CVE-2026-47221?

CVE-2026-47221 affects body-less non-GET/HEAD requests when handling HTTP 303 internal redirects.

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