Http4s up to 0.23.34/1.0.0-M46 CookieJar input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.89 |
Summary
A vulnerability, which was classified as problematic, has been found in Http4s up to 0.23.34/1.0.0-M46. Affected is an unknown function of the component CookieJar. Performing a manipulation results in input validation. This vulnerability is identified as CVE-2026-69215. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Http4s up to 0.23.34/1.0.0-M46. It has been classified as problematic. This affects an unknown functionality of the component CookieJar. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality. The summary by CVE is:
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The CookieJar client middleware uses unanchored substring checks instead of RFC 6265 domain and path matching when deciding whether to attach a stored cookie. A cookie for example.com can consequently be sent to an attacker-controlled hostname such as evilexample.com when an application using the same jar makes an attacker-influenced outbound request. This exposes session or authentication cookies and can enable hijacking of the application’s outbound sessions. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-69215 since 08/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.23.35 or 1.0.0-M47 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.8
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: Input validationCWE: CWE-20
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-69215 (🔒)
GCVE (CVE): GCVE-0-2026-69215
GCVE (VulDB): GCVE-100-404601
Entry
Created: 09/15/2026 21:44Changes: 09/15/2026 21:44 (63)
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.