Skip to content
Noroxi
CVE-2026-69205· NVD / CVE Program· CNA GitHub_M

Http4s: Ember Transfer-Encoding value parsing (TE.CL / TE.0 request smuggling)

Noroxi assessment

Priority: Monitor (action score 34/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: org.http4s:http4s-ember-core_2.12 (Maven) 0.23.35; org.http4s:http4s-ember-core_2.13 (Maven) 1.0.0-M47, 0.23.35; org.http4s:http4s-ember-core_3 (Maven) 1.0.0-M47, 0.23.35.

Low priority for now. Upgrade to org.http4s:http4s-ember-core_2.12 (Maven) 0.23.35; org.http4s:http4s-ember-core_2.13 (Maven) 1.0.0-M47, 0.23.35; org.http4s:http4s-ember-core_3 (Maven) 1.0.0-M47, 0.23.35 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, Ember’s HeaderP.parse uses a case-sensitive substring test for the Transfer-Encoding value and decodes header bytes with the platform default charset. Values such as Chunked are not recognized, values such as notchunked are incorrectly accepted, and Unicode case folding can turn a Kelvin-sign byte sequence into a match when UTF-8 is used. Intermediaries that apply RFC-compliant token and charset rules can therefore disagree with Ember’s Content-Length or zero-length framing, enabling TE.CL or TE.0 request smuggling, access-control bypass, cross-user request hijacking, and cache poisoning on the server path. Response smuggling through an ember-client gateway requires a malicious or compromised upstream. This issue is fixed in versions 0.23.35 and 1.0.0-M47.

HighCVSS 8.7 · v3.1—No exploit Fix available
Published
Sep 15, 2026
Updated
Sep 16, 2026
EPSS
0.4% · 39th percentile

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
8.7
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-69205

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • http4s http4s

    • < 0.23.35, >= 1.0.0-M1, < 1.0.0-M47affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.http4s:http4s-ember-core_2.12before 0.23.350.23.35
Mavenorg.http4s:http4s-ember-core_2.13from 1.0.0-M1 · before 1.0.0-M471.0.0-M47
Mavenorg.http4s:http4s-ember-core_2.13before 0.23.350.23.35
Mavenorg.http4s:http4s-ember-core_3from 1.0.0-M1 · before 1.0.0-M471.0.0-M47
Mavenorg.http4s:http4s-ember-core_3before 0.23.350.23.35

Other highest-scoring records for the same primary product.

  • CVE-2026-69204Http4s: Ember accepts Transfer-Encoding combined with Content-Length (CL.TE request smuggling)
    36Monitor
  • CVE-2026-69217Http4s: Ember Server accepts duplicate Content-Length headers
    34Monitor
  • CVE-2026-54556Http4s: HTTP/2 Denial of Service with Ember Backend
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-69202Sep 15, 2026 · Http4s Ember HTTP/2: unbounded inbound body buffering
    30Monitor
  • ← EarlierCVE-2026-69203Sep 15, 2026 · Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
    30Monitor
  • Later →CVE-2026-69206Sep 15, 2026 · Http4s: DigestAuth allows replay of captured requests
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.http4s:http4s-ember-core_2.120.23.35Package registry (OSV)
Maven:org.http4s:http4s-ember-core_2.130.23.35Package registry (OSV)
Maven:org.http4s:http4s-ember-core_2.131.0.0-M47Package registry (OSV)
Maven:org.http4s:http4s-ember-core_30.23.35Package registry (OSV)
Maven:org.http4s:http4s-ember-core_31.0.0-M47Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-692040 days apartHttp4s: Ember accepts Transfer-Encoding combined with Content-Length (CL.TE request smuggling)
    36Monitor
  • CVE-2026-692170 days apartHttp4s: Ember Server accepts duplicate Content-Length headers
    34Monitor
  • CVE-2026-692160 days apartHttp4s: Ember chunk parser lenience (TE.TE request smuggling)
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records