fix(deps): close the @hono/node-server advisory via SDK 1.30.0 - #70
Merged
Conversation
CVE sweep, 2026-07-29. GHSA-frvp-7c67-39w9 (path traversal in serve-static on Windows, `@hono/node-server` < 2.0.5) reached this repo transitively through `@modelcontextprotocol/sdk`. It was deferred on 2026-07-23 because the only fix then available was an SDK downgrade. SDK 1.30.0 now declares `@hono/node-server: ^1.19.9 || ^2.0.5`, so a within-major SDK minor (1.29.0 -> 1.30.0) lets hono resolve to 2.0.12. npm audit reported 2 moderate before this change and reports 0 after. Verification: npm ci, build and the full suite pass (233 tests). `npm install --package-lock-only` is a no-op, proving the lockfile is internally coherent. The lockfile delta is exactly two packages, @hono/node-server and @modelcontextprotocol/sdk, with no other churn. Note: hono 2.x raises `engines.node` to >=20. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
LanNguyenSi
added
review:tests-pass
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was und warum
CVE-Sweep 2026-07-29. Schliesst GHSA-frvp-7c67-39w9 (
@hono/node-server< 2.0.5,Path Traversal in
serve-staticauf Windows via encoded backslash%5C).Die Advisory kommt hier rein transitiv ueber
@modelcontextprotocol/sdk; diesesRepo deklariert
@hono/node-servernicht selbst. Am 2026-07-23 wurde sie deferrt,weil der einzige damals verfuegbare Fix ein SDK-Downgrade gewesen waere.
SDK 1.30.0 deklariert inzwischen
@hono/node-server: ^1.19.9 || ^2.0.5. EinMinor-Bump innerhalb von Major 1 (1.29.0 -> 1.30.0) reicht damit aus, hono loest auf
2.0.12 auf.
Betroffen ist
packages/memory-router.Verifikation
npm audit: 2 moderate vorher, 0 nachher.npm install --package-lock-onlyist ein No-op, das Lockfile ist in sich kohaerent.Einordnung
Der transitive Sprung hono 1.19.x -> 2.0.12 ist ein Major, unsere eigene Aenderung
aber ein Minor. Upstream deklariert die Kompatibilitaet explizit, und der Major liegt
vollstaendig innerhalb des SDK. Reale Exposure war hier ohnehin ~0: die Advisory ist
Windows-only und setzt
serveStaticvoraus, die Flotte laeuft auf Linux.hono 2.x hebt
engines.nodeauf >=20; geprueft, dieses Repo liegt darueber.Nicht in diesem PR: die fuenf Repos mit direkter hono-Dependency (echter Major auf
eigenem Servercode, Task
3906250f) und der upstream-blockiertebrace-expansion-Cluster (Task
5268025e).