Eclipse Grizzly up to 5.0.1 Trailer Parser request smuggling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 2.10+ |
Summary
A vulnerability, which was classified as problematic, has been found in Eclipse Grizzly up to 5.0.1. This affects an unknown part of the component Trailer Parser. The manipulation leads to request smuggling. This vulnerability is documented as CVE-2026-12606. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Eclipse Grizzly up to 5.0.1. This issue affects an unknown functionality of the component Trailer Parser. The manipulation with an unknown input leads to a request smuggling vulnerability. Using CWE to declare the problem leads to CWE-444. The product acts as an intermediary HTTP agent
(such as a proxy or firewall) in the data flow between two
entities such as a client and server, but it does not
interpret malformed HTTP requests or responses in ways that
are consistent with how the messages will be processed by
those entities that are at the ultimate destination. Impacted is integrity. The summary by CVE is:
Eclipse Grizzly in versions before 5.0.2, cannot properly parse the trailer section in malformed trailer header's line, which can be leveraged to perform HTTP request smuggling.
The advisory is shared at gitlab.eclipse.org. The identification of this vulnerability is CVE-2026-12606 since 06/18/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 5.0.2 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Request smugglingCWE: CWE-444
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Grizzly 5.0.2
Timeline
06/18/2026 CVE reserved07/14/2026 Advisory disclosed
07/14/2026 VulDB entry created
07/14/2026 VulDB entry last update
Sources
Advisory: gitlab.eclipse.orgStatus: Confirmed
CVE: CVE-2026-12606 (🔒)
GCVE (CVE): GCVE-0-2026-12606
GCVE (VulDB): GCVE-100-378281
Entry
Created: 07/14/2026 11:36Changes: 07/14/2026 11:36 (53)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.