CVE-2026-23527: H3 H3 V1 Has Request Smuggling Vulnerability
HIGHCVE-2026-23527 is a HIGH (CVSS 8.9) h3 v1 has request smuggling vulnerability (CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')) affecting H3 libraries in the npm ecosystem. The issue involves h3 v1 has request smuggling (te.te) issue. Remediation is available by upgrading affected packages to version 1.15.5.
CVE-2026-23527 at a Glance
Security Impact
CVSS: 8.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L).
How to Fix CVE-2026-23527
To remediate this vulnerability, upgrade all affected H3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install h3@1.15.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls h3
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-23527, inspect your project dependencies using npm:
npm ls h3
Analyze the terminal output to locate any version of H3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.15.5), your application is affected.
Note: The npm ls h3 command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'), where the product acts as an intermediary http agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed http requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. In H3, 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-23527 Affected H3 Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
h3
|
npm |
< 1.15.5
|
1.15.5
|
References
Frequently Asked Questions
What is CVE-2026-23527?
Which H3 versions are affected?
What version fixes CVE-2026-23527?
Is h3 affected?
What is the CVSS score of CVE-2026-23527?
What CWE is associated with CVE-2026-23527?
How can I check npm dependencies for CVE-2026-23527?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-mp2g-9vg9-f4cg",
"modified" : "2026-04-13T16:47:52Z",
"published" : "2026-01-15T20:10:51Z",
"aliases" : [ "CVE-2026-23527" ],
"summary" : "h3 v1 has Request Smuggling (TE.TE) issue",
"details" : "I was digging into h3 v1 (specifically v1.15.4) and found a critical HTTP Request Smuggling vulnerability.\n\nBasically, `readRawBody` is doing a strict case-sensitive check for the Transfer-Encoding header. It explicitly looks for \"chunked\", but per the RFC, this header should be case-insensitive.\n\n**The Bug**: If I send a request with Transfer-Encoding: ChuNked (mixed case), h3 misses it. Since it doesn't see \"chunked\" and there's no Content-Length, it assumes the body is empty and processes the request immediately.\n\nThis leaves the actual body sitting on the socket, which triggers a classic TE.TE Desync (Request Smuggling) if the app is running behind a Layer 4 proxy or anything that doesn't normalize headers (like AWS NLB or Node proxies).\n\n**Vulnerable Code** (`src/utils/body.ts`):\n\n```js\nif (\n !Number.parseInt(event.node.req.headers[\"content-length\"] || \"\") &&\n !String(event.node.req.headers[\"transfer-encoding\"] ?? \"\")\n .split(\",\")\n .map((e) => e.trim())\n .filter(Boolean)\n .includes(\"chunked\") // <--- This is the issue. \"ChuNkEd\" returns false here.\n ) {\n return Promise.resolve(undefined);\n }\n```\n\nI verified this locally:\n\n- Sent a `Transfer-Encoding: ChunKed` request without a closing 0 chunk.\n- Express hangs (correctly waiting for data).\n- h3 responds immediately (vulnerable, thinks body is length 0).\n\n**Impact**: Since H3/Nuxt/Nitro is often used in containerized setups behind TCP load balancers, an attacker can use this to smuggle requests past WAFs or desynchronize the socket to poison other users' connections.\n\n**Fix**: Just need to normalize the header value before checking: ` .map((e) => e.trim().toLowerCase())`",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "h3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.15.5"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.15.4"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/h3js/h3/security/advisories/GHSA-mp2g-9vg9-f4cg"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-23527"
}, {
"type" : "WEB",
"url" : "https://github.com/h3js/h3/commit/618ccf4f37b8b6148bea7f36040471af45bfb097"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/h3js/h3"
}, {
"type" : "WEB",
"url" : "https://github.com/h3js/h3/releases/tag/v1.15.5"
}, {
"type" : "WEB",
"url" : "https://simonkoeck.com/writeups/h3-transfer-encoding-request-smuggling"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-444" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-01-15T20:10:51Z",
"nvd_published_at" : "2026-01-15T20:16:05Z"
}
}