envoyproxy envoy up to 1.35.12/1.36.8/1.37.4/1.38.2 Connect Protocol null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in envoyproxy envoy up to 1.35.12/1.36.8/1.37.4/1.38.2. This vulnerability affects unknown code of the component Connect Protocol. The manipulation leads to null pointer dereference. This vulnerability is listed as CVE-2026-47204. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in envoyproxy envoy up to 1.35.12/1.36.8/1.37.4/1.38.2 and classified as problematic. This issue affects an unknown functionality of the component Connect Protocol. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:
Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.26.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, the envoy.filters.http.grpc_stats filter crashes (null pointer dereference / segfault) when a Connect protocol request (Content-Type: application/connect+proto or application/connect+json) hits a direct_response route. A single unauthenticated HTTP request crashes the Envoy process. This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-47204 since 05/19/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.35.13, 1.36.9, 1.37.5 or 1.38.3 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 1.35.0
- 1.35.1
- 1.35.2
- 1.35.3
- 1.35.4
- 1.35.5
- 1.35.6
- 1.35.7
- 1.35.8
- 1.35.9
- 1.35.10
- 1.35.11
- 1.35.12
- 1.36.0
- 1.36.1
- 1.36.2
- 1.36.3
- 1.36.4
- 1.36.5
- 1.36.6
- 1.36.7
- 1.36.8
- 1.37.0
- 1.37.1
- 1.37.2
- 1.37.3
- 1.37.4
- 1.38.0
- 1.38.1
- 1.38.2
License
Website
- Product: https://github.com/envoyproxy/envoy/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: envoy 1.35.13/1.36.9/1.37.5/1.38.3
Timeline
05/19/2026 CVE reserved06/26/2026 Advisory disclosed
06/26/2026 VulDB entry created
06/26/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-3jxh-8p6x-7pf6
Status: Confirmed
CVE: CVE-2026-47204 (🔒)
GCVE (CVE): GCVE-0-2026-47204
GCVE (VulDB): GCVE-100-374333
Entry
Created: 06/26/2026 21:22Changes: 06/26/2026 21:22 (66)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.