CVE-2026-48040: Netty incubator codec ohttp hpke native boringssl Netty-incubator-codec-ohttp's Incorrect Native Pointer Derivation Vulnerability
MODERATECVE-2026-48040 is a MODERATE netty-incubator-codec-ohttp's incorrect native pointer derivation vulnerability (CWE-125: Out-of-bounds Read) affecting Netty incubator codec ohttp hpke native boringssl libraries in the Maven ecosystem. The issue involves netty-incubator-codec-ohttp's incorrect native pointer derivation in pooled direct bytebuf fallback leads to out-of-bounds native memory access. Remediation is available by upgrading affected packages to version 0.0.22.Final.
CVE-2026-48040 at a Glance
How to Fix CVE-2026-48040
To remediate this vulnerability, upgrade all affected Netty incubator codec ohttp hpke native boringssl dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>io.netty.incubator</groupId>
<artifactId>netty-incubator-codec-ohttp-hpke-native-boringssl</artifactId>
<version>0.0.22.Final</version>
</dependency>Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=io.netty.incubatorHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-48040, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=io.netty.incubatorAnalyze the terminal output to locate any version of Netty incubator codec ohttp hpke native boringssl in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.22.Final), your application is affected.
Note: The mvn dependency:tree -Dincludes=io.netty.incubator command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-125: Out-of-bounds Read, where the product reads data past the end, or before the beginning, of the intended buffer. In Netty incubator codec ohttp hpke native boringssl, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-48040 Affected Netty incubator codec ohttp hpke native boringssl Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl
|
Maven |
< 0.0.22.Final
|
0.0.22.Final
|
References
Frequently Asked Questions
What is CVE-2026-48040?
Which Netty incubator codec ohttp hpke native boringssl versions are affected?
What version fixes CVE-2026-48040?
Is netty-incubator-codec-ohttp-hpke-native-boringssl affected?
What CWE is associated with CVE-2026-48040?
How can I check Maven dependencies for CVE-2026-48040?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-32hf-8jw3-v4qq",
"modified" : "2026-06-11T13:28:37Z",
"published" : "2026-06-11T13:28:37Z",
"aliases" : [ "CVE-2026-48040" ],
"summary" : "netty-incubator-codec-ohttp's Incorrect Native Pointer Derivation in Pooled Direct ByteBuf Fallback Leads to Out-of-Bounds Native Memory Access",
"details" : "The netty-incubator-codec-ohttp library implements Oblivious HTTP (RFC 9458) using BoringSSL's HPKE C library via JNI. When deriving native memory addresses for cryptographic operations, provides a fallback path for direct ByteBufs that do not expose their memory address through `hasMemoryAddress()`. This fallback occurs when `sun.misc.Unsafe` is unavailable to Netty — for example, when the JVM is started with `-Dio.netty.noUnsafe=true`, when a SecurityManager restricts Unsafe access, or when running on non-HotSpot JVMs. In these configurations, Netty's default `PooledByteBufAllocator` returns `PooledDirectByteBuf` instances for which `hasMemoryAddress()` returns false.\n\n**Why this matters:** Under the enabling JVM configuration, an unauthenticated network attacker can cause the OHTTP gateway to corrupt memory belonging to other concurrent connections and disclose the contents of adjacent pooled direct buffers by triggering cryptographic operations with crafted OHTTP requests. The corruption occurs regardless of whether the AEAD tag verification succeeds, as BoringSSL zeroizes the output buffer on failure. The information disclosure path provides the attacker with the encryption key needed to extract the leaked data. This violates the confidentiality and integrity of all connections sharing the same Netty buffer arena.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:U"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.0.22.Final"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-32hf-8jw3-v4qq"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48040"
}, {
"type" : "WEB",
"url" : "https://github.com/netty/netty-incubator-codec-ohttp/commit/7ad38d5cc2827af7e067e5c1e1ac37cd4566dad9"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/netty/netty-incubator-codec-ohttp"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-125" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-11T13:28:37Z",
"nvd_published_at" : "2026-06-04T18:16:31Z"
}
}