Tested on Node 22.23.4 and npm 10.9.9

Hono CVE-2026-126343: why npm audit stays red under the MCP SDK

Your CI fails on hono, @hono/node-server, or both, even though you did not add a Hono server. Updating one package can leave the other's alerts open. An existing override can also keep an affected version installed after an ordinary update.

There are two packages to check. The five Hono advisories published on 12 November are fixed in Hono 4.13.16. The two new Node adapter advisories are fixed in @hono/node-server 2.1.6; the backslash advisory also has a 1.19.18 fix on the 1.x line. These are advisory-specific first fixes, not a statement that those releases have no other vulnerabilities.

For an npm project using @modelcontextprotocol/sdk 1.32.2, the SDK declares hono ^4.11.4 and @hono/node-server ^1.19.9 || ^2.0.5. Those ranges admit patched releases. This is different from a parent that excludes the fix: inspect the installed lock and your own override before assuming the SDK needs another release.

Identify both copies and the restriction

Run these from the directory that owns the affected npm manifest and lockfile, after installing its locked dependencies:

node --version
npm --version
npm ls hono @hono/node-server @modelcontextprotocol/sdk
npm explain hono
npm explain @hono/node-server
npm pkg get overrides
npm audit --json
npm audit --omit=dev

An audit's nonzero exit status can mean it found a vulnerability. Read the report, including each advisory URL, rather than treating every red exit as an installation failure.

npm explain identifies the parent path. npm ls shows installed copies; check all of them. npm pkg get overrides shows your root override rules. A stale lockfile and an exact override are different restrictions: an update can move the former, while the latter keeps selecting the version you specified.

Compare the full audit with npm audit --omit=dev. Disappearing from the second report means exclusion from npm's non-development dependency report for that installation. It does not establish what your built image contains, which code CI runs, or whether an application can reach a vulnerable function.

This page's commands target npm. Yarn, pnpm and Bun have their own lockfiles and override settings. Changing an npm lockfile does not repair another package manager's lockfile, another workspace's separate lock, a globally installed tool or an already built artifact.

Account for the whole wave

The following are GitHub's advisory ranges, checked on 14 November. The descriptions summarize those advisories; they are not our own reachability-test results. Review the complete audit from your own tree; an older installed version may have additional findings.

  • CVE-2026-126343 / GHSA-qv5m-9pm6-hqp3 — @hono/node-server >=2.0.0, <2.1.6; first fixed 2.1.6. The advisory describes an unhandled socket error during an asynchronous WebSocket upgrade, which can terminate the process; it applies where WebSocket support is enabled and asynchronous middleware or handlers run on the upgrade path.
  • CVE-2026-126210 / GHSA-jpvv-r467-5p4w — @hono/node-server <1.19.18 or >=2.0.0, <2.1.6; first fixes 1.19.18 / 2.1.6. A raw backslash can make the adapter and a front proxy interpret the path differently, bypassing that proxy's path-based access restriction.
  • CVE-2026-126355 / GHSA-46wx-v44x-9hh2 — hono <4.13.16; first fixed 4.13.16. The CSRF middleware skips checks for hyperlink-auditing requests with text/ping.
  • CVE-2026-126356 / GHSA-4h7h-rv7c-7m2v — hono >=4.5.1, <=4.13.15; first fixed 4.13.16. Some multipart content types bypass the form parser used by validation; an accepting empty-object callback can let fields reach a handler without that validation.
  • CVE-2026-126357 / GHSA-4m76-xfj5-7975 — hono <4.13.16; first fixed 4.13.16. Mounted paths can reach an inner route without the outer path-scoped middleware intended to protect it.
  • CVE-2026-126358 / GHSA-h7mg-cq63-vhpq — hono >=4.1.4, <=4.13.15; first fixed 4.13.16. RegExpRouter can skip wildcard middleware for particular route patterns or encoded line terminators.
  • CVE-2026-126359 / GHSA-3gg2-335m-rxc6 — hono >=3.12.0, <=4.13.15; first fixed 4.13.16. The CSS helper can permit HTML injection when a closing tag is split across a template boundary and an outside-controlled value.

GitHub rates the CSS-helper advisory Low and the other six Moderate. A scanner may report a parent package as affected through its dependency too; that does not necessarily mean another independent bug.

If the lockfile is stale and there is no blocking override

For the SDK ranges above, ask npm to update both packages, then inspect the resulting tree and audit:

npm update hono @hono/node-server --ignore-scripts
npm ls hono @hono/node-server
npm audit

Review the manifest and lockfile diff. This is not a promise that only two entries will change in your project. If either package remains old, read its parent range and overrides. Do not use a force flag before understanding the proposed dependency change.

If the audit is still red afterwards, look for the seven advisory URLs listed above; npm prints each one beside its finding. If none of them remains, the Hono and adapter findings are cleared, and what is left is a separate advisory with its own fix.

An ordinary npm audit fix --ignore-scripts is another npm remediation command. It cannot be assumed to replace an exact override you own. Check the actual versions afterward.

If an old root override keeps the alert open

On 14 November, the latest published versions were hono 4.13.18 and @hono/node-server 2.1.8. The example below is for projects where both affected packages are transitive, the adapter is already on 2.x, and every affected parent accepts these versions. Both versions satisfy the SDK 1.32.2 ranges above.

For simple, flat root overrides, update the two settings together:

npm pkg set 'overrides.hono=4.13.18' 'overrides.@hono/node-server=2.1.8'
npm install --ignore-scripts
npm ls hono @hono/node-server
npm audit

These settings apply throughout the npm dependency tree. Preserve your other overrides. If an existing rule is nested, version-scoped or an object, edit that actual rule instead of blindly adding these keys. If either package is a direct dependency, update its dependency declaration first and resolve any matching override: npm restricts overriding direct dependencies.

Do not apply this 2.x override to an adapter 1.x project without a separate compatibility decision. The backslash advisory lists 1.19.18 for that line; this page has not tested the 1.x remedy.

--ignore-scripts skips install scripts. It does not test your build, HTTP routing or WebSocket behavior. Run your normal build and the actual tool or transport that brought in the packages, under your installation policy, before accepting and committing the manifest and lockfile. Record why the override exists and when it can be removed.

What we tested, and what remains your decision

We ran every shell block above on Node 22.23.4 / npm 10.9.9 in an official, digest-pinned Linux container. Both small fixture projects installed SDK 1.32.2 as a development dependency, with Hono 4.13.13 and the adapter 2.1.5 initially installed.

  • Stale lock, no override: updating the two packages resolved Hono 4.13.18 and the adapter 2.1.8, and the full audit returned zero findings.
  • Exact old overrides: the update left 4.13.13 and 2.1.5 installed (npm reported "up to date"), and the block ended with exit 1 because its final audit still reported the findings. The subsequent ordinary audit fix also exited 1 and retained those versions. Its report still said a fix was available; that did not mean it had applied one.
  • Updating both overrides: in the exact-override fixture the recipe changed both packages to 4.13.18 and 2.1.8; in the stale-lock fixture those versions were already installed from the update, and the recipe left them in place. In both, the full audit returned zero findings before and after a locked reinstall with install scripts disabled.

Both before-audits included all seven advisory URLs listed above. npm grouped them into two package findings in one fixture and three in the other; the latter included an inherited SDK finding. The non-development audit returned zero even before the fixes, because the SDK was installed as a development dependency. This illustrates the report filter, not an exposure clearance. These clean results apply to the fixture trees, not to your project.

The commands inspect dependency resolution and audit results. They do not classify your application's reachability. We did not reproduce these seven vulnerabilities or test an exploit mitigation, a real MCP client, HTTP/WebSocket transport behavior, or the hosted Dependabot interface. An installed SDK alone does not answer which transports and routes your application uses. A stdio-only claim needs evidence about the program and the artifact you actually deploy.

If you defer a fix, review each advisory's conditions separately, trace the application's actual imports and running transports, and record the installed version, advisory, exposure evidence, owner and next review condition. A clean grep or an omitted dev dependency is insufficient evidence for dismissal. When you update, rerun the full audit: clearing only CVE-2026-126343 does not clear the Hono findings.

For a Dependabot alert, also check its named manifest and the fixed lockfile on the repository's default branch. GitHub documents its alert lifecycle in Viewing and updating Dependabot alerts. We have not tested the service's closing behavior for these fixtures.

Keep the next dependency change visible

Check your project's next dated software change

No email address is needed.

Corrections: hello@cybernative.ai. We publish dated corrections when a material claim changes.