How severe is GHSA-f659-372h-6x3x?

No CVSS score has been assigned to GHSA-f659-372h-6x3x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f659-372h-6x3x?

GHSA-f659-372h-6x3x affects the following packages: io.netty.incubator:netty-incubator-codec-ohttp (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f659-372h-6x3x?

Update io.netty.incubator:netty-incubator-codec-ohttp to 0.0.21.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f659-372h-6x3x is resolved across your whole dependency graph.

How do I detect GHSA-f659-372h-6x3x 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-f659-372h-6x3x 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-f659-372h-6x3x actively exploited in the wild?

No public exploit code has been indexed for GHSA-f659-372h-6x3x 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-f659-372h-6x3x?

GHSA-f659-372h-6x3x has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th 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-f659-372h-6x3x?

GHSA-f659-372h-6x3x is classified as Insufficient Random Values (CWE-330). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f659-372h-6x3x published, and has it been updated?

GHSA-f659-372h-6x3x was published on May 26, 2026 and was last updated on June 9, 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

netty-incubator-codec-ohttp's HPKEContext operations may produce empty byte[] on failuresGHSA-f659-372h-6x3x

Fix: netty/netty-incubator-codec-ohttp@3d3b4e5

GHSA-f659-372h-6x3x is a Insufficient Random Values 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-41207

Published

May 26, 2026

Updated

Jun 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 7, 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-f659-372h-6x3x.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% 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.21.Final, HKDF_expand returns non-NULL on failure. The byte[] is filled with zeros and has no way to distinguish success from failure. Since this output is used as HKDF key material for the response AEAD, a failure silently produces an all-zero key. When EVP_HPKE_CTX_export fails it also returns an empty byte[] array filled with zeros. This byte[] feeds directly into OHttpCrypto.createResponseAEAD(...). A silent all-zero export secret would produce a deterministic, attacker-predictable AEAD key. Version 0.0.21.Final patches 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.21.Final`io.netty.incubator:netty-incubator-codec-ohttp:0.0.21.Final`

Affected Products

1 product · 1 configurations

Application

netty-incubator-codec-ohttpnetty

< 0.0.21

range

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.21.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f659-372h-6x3x 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

HKDF_expand: returns non-NULL on failure. The byte[] is filled with zeros and has no way to distinguish success from failure. Since this output is used as HKDF key material for the response AEAD, a failure silently produces an all-zero key. When EVP_HPKE_CTX_export fails it also returns an empty byte[] array filled with zeros. This byte[] feeds directly into OHttpCrypto.createResponseAEAD(...). A silent all-zero export secret would produce a deterministic, attacker-predictable AEAD key.

O3 Security · Impact-Aware SCA

Is GHSA-f659-372h-6x3x in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works