http4s up to 0.23.34/1.0.0-M46 Ember request smuggling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.89- |
Summary
A vulnerability, which was classified as problematic, was found in http4s up to 0.23.34/1.0.0-M46. Affected by this vulnerability is an unknown functionality of the component Ember. Executing a manipulation can lead to request smuggling. This vulnerability is tracked as CVE-2026-69217. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in http4s up to 0.23.34/1.0.0-M46. It has been declared as problematic. This vulnerability affects some unknown functionality of the component Ember. The manipulation with an unknown input leads to a request smuggling vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. CVE summarizes:
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, Ember’s HTTP/1.1 parser accepts differing duplicate Content-Length headers and uses the last value instead of rejecting the message. When an Ember server is behind a keep-alive intermediary that selects a different occurrence, an unauthenticated attacker can create CL.CL request smuggling that bypasses front-end controls, captures a later user’s headers, or poisons a cache. The shared client parser can also misframe responses from a malicious or compromised upstream when the client acts as a proxy for multiple downstream consumers. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
The advisory is available at github.com. This vulnerability was named CVE-2026-69217 since 08/03/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 0.23.35 or 1.0.0-M47 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 0.23.0
- 0.23.1
- 0.23.2
- 0.23.3
- 0.23.4
- 0.23.5
- 0.23.6
- 0.23.7
- 0.23.8
- 0.23.9
- 0.23.10
- 0.23.11
- 0.23.12
- 0.23.13
- 0.23.14
- 0.23.15
- 0.23.16
- 0.23.17
- 0.23.18
- 0.23.19
- 0.23.20
- 0.23.21
- 0.23.22
- 0.23.23
- 0.23.24
- 0.23.25
- 0.23.26
- 0.23.27
- 0.23.28
- 0.23.29
- 0.23.30
- 0.23.31
- 0.23.32
- 0.23.33
- 0.23.34
- 1.0.0-M46
Website
- Product: https://github.com/http4s/http4s/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.7
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: 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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: http4s 0.23.35/1.0.0-M47
Timeline
08/03/2026 CVE reserved09/15/2026 Advisory disclosed
09/15/2026 VulDB entry created
09/15/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-69217 (🔒)
GCVE (CVE): GCVE-0-2026-69217
GCVE (VulDB): GCVE-100-404602
Entry
Created: 09/15/2026 21:45Changes: 09/15/2026 21:45 (63)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.