CVE-2026-50572: Envoy: ext_authz - RawHttpClientImpl onSuccess 0x0 segfault

Published Sep 21, 2026
·
Updated

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's HTTP external-authorization client can retain a stale request callback after a request is rejected. When RawHttpClientImpl::onSuccess later processes the authorization response, it can invoke callbacks after the callback owner has been destroyed, causing a use-after-free and process crash under production traffic. The relevant scope boundary is that the vulnerable path uses the HTTP extauthz client; the advisory does not establish the same trigger for unrelated filters. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.

Affected Software

1 affected component
Envoy Envoy<1.36.10, >1.36.10<=1.37.6, >1.37.6<=1.38.4, >1.38.4<=1.39.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.36.10
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.37.6
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.38.4
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.39.1

Event History

Sep 21, 2026
CVE Published
via MITRE·07:32 PM
Data Sourced
via MITRE·07:32 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which Envoy deployments are exposed to this issue?

Deployments using the HTTP external-authorization (ext_authz) client are in scope if they run a version earlier than 1.36.10, 1.37.6, 1.38.4, or 1.39.1. The advisory does not establish the same trigger for unrelated filters.

2

What conditions are needed for exploitation?

A request must be rejected in a way that leaves a stale request callback, followed by processing of the authorization response in RawHttpClientImpl::onSuccess after the callback owner has been destroyed. The resulting use-after-free can crash the Envoy process under production traffic.

3

What should be done to remediate the issue?

Upgrade Envoy to 1.36.10, 1.37.6, 1.38.4, or 1.39.1, as appropriate for the release line in use.

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