Security readout for executives and security teams
Plain-English summary
CVE-2026-23527 affects h3, a JavaScript HTTP framework. Older versions mishandle Transfer-Encoding header casing, creating a request smuggling risk. In affected deployments, attackers may cause front-end and back-end HTTP components to disagree about request boundaries. This can threaten confidentiality and integrity. The vendor states the issue is fixed in h3 1.15.5.
Executive priority
Treat as a high-priority dependency update for exposed web applications using h3. Business urgency is highest where h3-backed services sit behind proxies or gateways. No active exploitation is confirmed in the provided sources, but the potential data impact is significant.
Technical view
h3 versions before 1.15.5 perform a strict case-sensitive check for the Transfer-Encoding value "chunked" in readRawBody, despite RFC case-insensitivity. The advisory describes this as a critical HTTP Request Smuggling TE.TE issue, mapped to CWE-444. CVSS is 8.9 with network attack vector, no privileges or user interaction, high confidentiality and integrity impact, and high attack complexity.
Likely exposure
Exposure is most likely in Node.js applications or frameworks that directly or transitively depend on h3 versions earlier than 1.15.5 and process HTTP requests behind proxies, gateways, load balancers, or other HTTP intermediaries.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Public write-up material exists, but this assessment should not treat exploitation as observed. Request smuggling impact depends heavily on deployment architecture and intermediary behavior.
Researcher notes
Focus analysis on h3 readRawBody behavior before 1.15.5 and environments with multiple HTTP parsers. Avoid assuming exploitability without matching proxy and application behavior. The fixing commit and release notes are the key primary sources for code-level verification.
Mitigation direction
- Upgrade h3 to version 1.15.5 or later.
- Check transitive dependencies that may bundle or pin h3 below 1.15.5.
- Review vendor advisory and release notes for project-specific guidance.
- Prioritize internet-facing services behind HTTP intermediaries.
Validation and detection
- Search package manifests and lockfiles for h3 versions below 1.15.5.
- Use software composition analysis to identify transitive h3 usage.
- Confirm deployed artifacts match updated dependency versions.
- Review edge, proxy, and application architecture for HTTP request parsing chains.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-444: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23527 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L2.26Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.9HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/h3js/h3/security/advisories/GHSA-mp2g-9vg9-f4cgCVE reference · x_refsource_CONFIRM
- https://github.com/h3js/h3/commit/618ccf4f37b8b6148bea7f36040471af45bfb097CVE reference · x_refsource_MISC
- https://github.com/h3js/h3/releases/tag/v1.15.5CVE reference · x_refsource_MISC
- https://simonkoeck.com/writeups/h3-transfer-encoding-request-smugglingCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.