Summary
OHttpVersionChunkDraft: Missing Final-Chunk Enforcement Leads to Undetected Stream Truncation
The codec-ohttp implementation of draft-ietf-ohai-chunked-ohttp does not verify that a cryptographically-signed final chunk was received before the outer HTTP body terminates. An on-path adversary (the OHTTP relay itself, or any MITM on the relay↔gateway or relay↔client transport) can forward a prefix of a legitimate chunked-OHTTP message, cut at a non-final chunk boundary, and close the outer body cleanly, producing no decryption error and no exception in the receiving application.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-48480? CVE-2026-48480 is a medium-severity security vulnerability in io.netty.incubator:netty-incubator-codec-ohttp (maven), affecting versions < 0.0.22.Final. It is fixed in 0.0.22.Final.
- Which versions of io.netty.incubator:netty-incubator-codec-ohttp are affected by CVE-2026-48480? io.netty.incubator:netty-incubator-codec-ohttp (maven) versions < 0.0.22.Final is affected.
- Is there a fix for CVE-2026-48480? Yes. CVE-2026-48480 is fixed in 0.0.22.Final. Upgrade to this version or later.
- Is CVE-2026-48480 exploitable, and should I be worried? Whether CVE-2026-48480 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-48480 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-48480? Upgrade
io.netty.incubator:netty-incubator-codec-ohttpto 0.0.22.Final or later.