Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5

Envoy crashes when HTTP ext_proc processes local replies

CVE-2025-30157GHSA-cf3q-gqg7-3fm9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/envoyproxy/envoy 1.33.1, 1.32.4, 1.31.6, 1.30.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/envoyproxy/envoy

    Affected
    < 1.30.10>= 1.31.0, < 1.31.6>= 1.32.0, < 1.32.4>= 1.33.0, < 1.33.1
    Fixed in
    1.33.1, 1.31.6, 1.30.10, 1.32.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
  • CVE-2025-30157: 0.44% estimated exploitation activity in the next 30 days; percentile 37.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Envoy's extproc HTTP filter is at risk of crashing if a local reply is sent to the external server due to the filter's life time issue. A known situation is the fail of a websocket handshake will trigger a local reply leading to the crash of Envoy. PoC If both websocket and extproc are enabled, a failed handshake will trigger a local reply, thus extproc will crash. Mitigation 1. Disable websocket traffic 2. Change the websocket response from backend to always return 101 Switch protocol based on RFC. 3. Apply the patch and the extproc filter will not send the local reply that is generated by Envoy to the extproc server for processing. 4. Apply the patch that the router will cancel the upstream requests when sending a local reply. Impact Denial of service Reporter Vasilios Syrakis Fernando Cainelli

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-cf3q-gqg7-3fm9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-30157

Advisory: Envoy crashes when HTTP ext_proc processes local replies
IDs: CVE-2025-30157, GHSA-cf3q-gqg7-3fm9
Record: https://patchnext.com/advisories/cve-2025-30157 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/envoyproxy/envoy 1.33.1, 1.32.4, 1.31.6, 1.30.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/envoyproxy/envoy: affected < 1.30.10; >= 1.31.0, < 1.31.6; >= 1.32.0, < 1.32.4; >= 1.33.0, < 1.33.1; fixed in 1.33.1, 1.31.6, 1.30.10, 1.32.4

## Suggested inspection (read-only)
- Go github.com/envoyproxy/envoy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/envoyproxy/envoy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cf3q-gqg7-3fm9 (GitHub-reviewed advisory GHSA-cf3q-gqg7-3fm9 lists affected ranges: Go github.com/envoyproxy/envoy >=0 =1.31.0 =1.32.0 =1.33.0 <1.33.1)

Commands are suggestions: review each one before running it.

Loading voting…