How severe is GHSA-r6fj-869h-4f6q?

No CVSS score has been assigned to GHSA-r6fj-869h-4f6q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r6fj-869h-4f6q?

GHSA-r6fj-869h-4f6q affects the following packages: io.netty.incubator:netty-incubator-codec-ohttp (Maven). Ecosystems affected: Maven.

How do I fix GHSA-r6fj-869h-4f6q?

Update io.netty.incubator:netty-incubator-codec-ohttp to 0.0.22.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6fj-869h-4f6q is resolved across your whole dependency graph.

How do I detect GHSA-r6fj-869h-4f6q in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty.incubator:netty-incubator-codec-ohttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-r6fj-869h-4f6q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-r6fj-869h-4f6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-r6fj-869h-4f6q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-r6fj-869h-4f6q?

GHSA-r6fj-869h-4f6q has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-r6fj-869h-4f6q?

GHSA-r6fj-869h-4f6q is classified as CWE-325 (CWE-325). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r6fj-869h-4f6q published, and has it been updated?

GHSA-r6fj-869h-4f6q was published on June 23, 2026 and was last updated on June 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

OHttpVersionChunkDraft: Missing Final-Chunk Enforcement Leads to Undetected Stream TruncationGHSA-r6fj-869h-4f6q

Fix: netty/netty-incubator-codec-ohttp@28f977f

GHSA-r6fj-869h-4f6q is a CWE-325 vulnerability in io.netty.incubator:netty-incubator-codec-ohttp. A fix is available for io.netty.incubator:netty-incubator-codec-ohttp — see the affected versions and patch details below.

Also known asCVE-2026-48480

Published

Jun 23, 2026

Updated

Jun 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r6fj-869h-4f6q.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕io.netty.incubator:netty-incubator-codec-ohttp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The netty incubator codec.bhttp is a java language binary http parser. Prior to version 0.0.22.FInal, 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. Version 0.0.22.Final fixes the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.netty.incubator:netty-incubator-codec-ohttp`	all versions	0.0.22.Final`io.netty.incubator:netty-incubator-codec-ohttp:0.0.22.Final`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty.incubator:netty-incubator-codec-ohttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.netty.incubator:netty-incubator-codec-ohttp to 0.0.22.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6fj-869h-4f6q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-r6fj-869h-4f6q in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works