deps: bump hono to >=4.12.34 (CVE-2026-69207, CORS ReDoS) - #461
Open
pcornelissen wants to merge 1 commit into
Open
deps: bump hono to >=4.12.34 (CVE-2026-69207, CORS ReDoS)#461pcornelissen wants to merge 1 commit into
pcornelissen wants to merge 1 commit into
Conversation
hono 4.12.30 is affected by CVE-2026-69207 / GHSA-8j4g-w8fx-2239 (ReDoS in the CORS middleware via Access-Control-Request-Headers), fixed in 4.12.34. - bump hono to ^4.12.34 in apps/api and apps/proxy - move the pinned pnpm override @modelcontextprotocol/sdk>hono to 4.12.34 so the transitive copy is not left on the vulnerable version - set an explicit allowHeaders on the /.well-known/* cors() block as defense in depth, so the reflect-and-parse path is not taken regardless of the hono version Fixes superloglabs#460
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
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.
What & why
hono4.12.30 is affected by CVE-2026-69207 / GHSA-8j4g-w8fx-2239 (ReDoS inthe CORS middleware via
Access-Control-Request-Headers), fixed in 4.12.34.The vulnerable path is reachable unauthenticated through the
/.well-known/*CORS block, which is the one
cors()call in the repo without an explicitallowHeaders. Details and reachability analysis are in #460.Fixes #460
This PR:
honoto^4.12.34inapps/apiandapps/proxy(pnpm resolves to 4.13.1)@modelcontextprotocol/sdk>honoto4.12.34, so thetransitive copy is not left on the vulnerable version after a normal update
allowHeaderson the/.well-known/*cors()block asdefense in depth, so the reflect-and-parse path is not taken regardless of the
hono version
How to test
pnpm why honoshows no remaining 4.12.30 resolutionpnpm typecheckpassespnpm lintpassesAI assistance
cors()call and drafting this change,as part of the KIberblick OSS security service. The CVE match and the fix were
verified by hand against
pnpm-lock.yamland the GHSA advisory.Type of change
Checklist
pnpm typecheckpassespnpm lintpassespnpm formathas been run on changed filesmainSummary by cubic
Upgrades
honoto >=4.12.34 and hardens the/.well-known/*CORS config to address CVE-2026-69207 (CORS ReDoS). Removes the vulnerable version from direct and transitive installs and blocks the reflect-and-parse path.Dependencies
honoto^4.12.34inapps/apiandapps/proxy.@modelcontextprotocol/sdk>honooverride to4.12.34to replace the transitive vulnerable copy.Bug Fixes
allowHeaders: ["Content-Type", "Authorization"]to the/.well-known/*cors()block for defense in depth.Written for commit 3a4d2dc. Summary will update on new commits.