Skip to content
Fencer Intel
medium 6.5

CVE-2025-30157 json

Envoy crashes when HTTP ext_proc processes local replies

published last yr. modified last mo. also BIT-envoy-2025-30157 , EUVD-2025-7242 , GHSA-cf3q-gqg7-3fm9

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

Envoy is a cloud-native high-performance edge/middle/service proxy. Prior to 1.33.1, 1.32.4, 1.31.6, and 1.30.10, Envoy's ext_proc 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 failure of a websocket handshake will trigger a local reply leading to the crash of Envoy. This vulnerability is fixed in 1.33.1, 1.32.4, 1.31.6, and 1.30.10.

Patch / fix

  • go github.com/envoyproxy/envoy 1.30.10, 1.31.6, 1.32.4, 1.33.1
  • bitnami envoy 1.30.10, 1.31.6, 1.32.4, 1.33.1
  • envoyproxy envoy 1.30.10, 1.31.6, 1.32.4, 1.33.1
  • istioctl openSUSE Tumbleweed 1.25.1-1.1

opensuse advisories openSUSE-SU-2025:14938-1

Is CVE-2025-30157 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-cf3q-gqg7-3fm9 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/envoyproxy/envoy
<1.30.10
>=1.31.0, <1.31.6
>=1.32.0, <1.32.4
>=1.33.0, <1.33.1
1.30.10
1.31.6
1.32.4
1.33.1
bitnami envoy
<1.30.10
>=1.31.0, <1.31.6
>=1.32.0, <1.32.4
>=1.33.0, <1.33.1
1.30.10
1.31.6
1.32.4
1.33.1

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-460 Improper Cleanup on Thrown Exception

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.