Advisories
This weekExploitable · Confirmed

h3: h3 has a middleware bypass with one gadget

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

h3 (npm)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • h3 (npm): from 2.0.0-0, before 2.0.1-rc.15

The fix

  • h3 (npm) fixed in 2.0.1-rc.15

    npm
    npm install h3@2.0.1-rc.15
    pnpm
    pnpm add h3@2.0.1-rc.15
    yarn
    yarn add h3@2.0.1-rc.15
    bun
    bun add h3@2.0.1-rc.15
    Check what is installed
    npm ls h3
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency h3 to 2.0.1-rc.15 or the nearest later release, to fix CVE-2026-33131. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))