CVE-2026-33129: H3 H3 Has An Observable Timing Vulnerability
MODERATECVE-2026-33129 is a MODERATE (CVSS 5.9) h3 has an observable timing vulnerability (CWE-208: Observable Timing Discrepancy) affecting H3 libraries in the npm ecosystem. The issue involves h3 has an observable timing discrepancy in basic auth utils. Remediation is available by upgrading affected packages to version 2.0.1-rc.9.
CVE-2026-33129 at a Glance
Security Impact
CVSS: 5.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:U/C:H/I:N/A:N).
How to Fix CVE-2026-33129
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@2.0.1-rc.9
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-33129, 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 2.0.1-rc.9), 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-208: Observable Timing Discrepancy, where two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not. 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-33129 Affected H3 Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
h3
|
npm |
≥ 2.0.0-beta.0
< 2.0.1-rc.9
|
2.0.1-rc.9
|
References
Frequently Asked Questions
What is CVE-2026-33129?
Which H3 versions are affected?
What version fixes CVE-2026-33129?
Is h3 affected?
What is the CVSS score of CVE-2026-33129?
What CWE is associated with CVE-2026-33129?
How can I check npm dependencies for CVE-2026-33129?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-26f5-8h2x-34xh",
"modified" : "2026-03-20T21:27:48Z",
"published" : "2026-03-18T16:17:58Z",
"aliases" : [ "CVE-2026-33129" ],
"summary" : "h3 has an observable timing discrepancy in basic auth utils",
"details" : "### Summary\nA Timing Side-Channel vulnerability exists in the `requireBasicAuth` function due to the use of unsafe string comparison (`!==`). This allows an attacker to deduce the valid password character-by-character by measuring the server's response time, effectively bypassing password complexity protections.\n\n### Details\nThe vulnerability is located in the `requireBasicAuth` function. The code performs a standard string comparison between the user-provided password and the expected password:\n\n~~~typescript\nif (opts.password && password !== opts.password) {\n throw autheFailed(event, opts?.realm);\n}\n~~~\n\nIn V8 (and most runtime environments), the `!==` operator is optimized to \"fail fast.\" It stops execution and returns `false` as soon as it encounters the first mismatched byte.\n* If the first character is wrong, it returns immediately.\n* If the first character is correct but the second is wrong, it takes slightly longer.\n\nBy statistically analyzing these minute timing differences over many requests, an attacker can determine the correct password one character at a time.\n\n### PoC\nThis vulnerability is exploitable in real-world scenarios without direct access to the server machine.\n\nTo reproduce this, an attacker can send two packets (or bursts of packets) at the exact same time:\n1. **Packet A:** Contains a password that is known to be incorrect starting at the first character (e.g., `AAAA...`).\n2. **Packet B:** Contains a password where the first character is a guess (e.g., `B...`).\n\nBy measuring the time-to-first-byte (TTFB) or total response time of these concurrent requests, the attacker can filter out network jitter. If Packet B takes consistently longer to return than Packet A, the first character is confirmed as correct. This process is repeated for the second character, and so on. Tests confirm this timing difference is statistically consistent enough to recover credentials remotely.\n\n### Impact\n\nThis vulnerability allows remote attackers to recover passwords. While network jitter makes this difficult over the internet, it is highly effective in local networks or cloud environments where the attacker is co-located. It reduces the complexity of cracking a password from exponential (guessing the whole string) to linear (guessing one char at a time).",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "h3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0-beta.0"
}, {
"fixed" : "2.0.1-rc.9"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.0.0-rc.8"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/h3js/h3/security/advisories/GHSA-26f5-8h2x-34xh"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33129"
}, {
"type" : "WEB",
"url" : "https://github.com/h3js/h3/pull/1283"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/h3js/h3"
}, {
"type" : "WEB",
"url" : "https://github.com/h3js/h3/releases/tag/v2.0.1-rc.9"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-208" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-18T16:17:58Z",
"nvd_published_at" : "2026-03-20T10:16:19Z"
}
}