What is the CVSS score of CVE-2026-69216?

CVE-2026-69216 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2026-69216?

Yes, a public proof-of-concept exploit is available for CVE-2026-69216. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2026-69216?

Yes, a patch is available for CVE-2026-69216. Update the affected software to the latest version immediately.

Http4s CVE-2026-69216

EUVD-2026-79176 MEDIUM

HTTP Request/Response Smuggling (CWE-444)

2026-09-15 security-advisories@github.com

GHSA-jrpm-956j-96jg

Authentication Bypass Request Smuggling

5.4

CVSS 3.1 · Vendor: github

View

Vulnerability Assessment

Weakness

CWE

CWE-444

OWASP Top 10:2025

A06:2025 - Insecure Design

ASVS 5.0

V4 - API and Web Service HTTP request consistency

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).

Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 15, 2026

Request smuggling in http4s Ember affects ember-core (server and client) before 0.23.35 and 1.0.0-M47 because the chunked decoder trims chunk-size tokens and accepts leading '+' or '-' signs instead of requiring hexadecimal digits followed by the mandatory CRLF. When Ember runs behind an intermediary that forwards chunked bodies without re-encoding and parses chunk boundaries differently, an unauthenticated attacker can achieve TE.TE request smuggling that bypasses intermediary controls, poisons shared caches, or hijacks queued requests; the same response-path leniency enables response smuggling when ember-client is used as a gateway in front of a malicious or compromised upstream. No public exploit code or CISA KEV entry is associated with this issue at time of analysis, and no EPSS score was supplied in the source data.

Affected VersionsENISA

http4s 1.0.0-M1, < 1.0.0-M47

http4s < 0.23.35

Affected Packages

maven org.http4s:http4s-ember-core_2.12 fix: 0.23.35

maven org.http4s:http4s-ember-core_2.13 fix: 0.23.35, 1.0.0-M47

maven org.http4s:http4s-ember-core_3 fix: 0.23.35, 1.0.0-M47

euvd http4s fix: 0.23.35

euvd http4s_1_0_0_m1 fix: 1.0.0-M47

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 5 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 5.4 MEDIUM

AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Primary rating from Vendor (github) · only source for this CVE.

CVSS VectorVendor: github

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Patch available

Sep 15, 2026 - 20:19 EUVD

DescriptionCVE.org

Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, Ember’s chunk decoder trims the chunk-size token and accepts leading plus or minus signs instead of requiring one or more hexadecimal digits followed by the required CRLF. When an intermediary forwards chunked data without re-encoding and interprets malformed chunk boundaries differently, an unauthenticated attacker can create TE.TE request smuggling that bypasses intermediary controls, poisons caches, or hijacks the request queue. The same response-path leniency can enable response smuggling against an ember-client used as a gateway when the upstream is malicious or compromised. This issue is fixed in versions 0.23.35 and 1.0.0-M47.

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

3 maven packages depend on org.http4s:http4s-ember-core_2.12 (2 direct, 1 indirect)

Ecosystem-wide dependent count for version 0.23.35.

Threat Intelligence Overview

EPSS Score

0.2%

Top 84% exploitable

Threat Intel

1 source

Exploit

POC

Public exploit code exists

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS GHSA

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity MEDIUM

CISA KEV No

Public POC Yes

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

MEDIUM severity (CVSS 4.0-6.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.