fix: upgrade hono to ^4.12.18 to address CVE-2026-44455#1188
fix: upgrade hono to ^4.12.18 to address CVE-2026-44455#1188brendan-kellam wants to merge 2 commits intomainfrom
Conversation
Co-authored-by: Brendan Kellam <brendan@sourcebot.dev>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-authored-by: Brendan Kellam <brendan@sourcebot.dev>
License Audit
Weak Copyleft Packages (informational)
Resolved Packages (11)
|
|
Closing as duplicate — consolidated into #1186, which addresses all four sibling hono CVEs (44455–44458) with the same 4.12.14 → 4.12.18 bump. |
Fixes SOU-1068
Summary
Upgrades
honoto^4.12.18to address CVE-2026-44455, CVE-2026-44456, CVE-2026-44457, CVE-2026-44458, and CVE-2026-44459.Details
CVE-2026-44455: hono/jsx Unvalidated JSX Tag Names Allow HTML Injection
The
honopackage (v4.12.14) had a vulnerability where untrusted input used as JSX element tag names via the programmaticjsx()orcreateElement()APIs during server-side rendering could inject unintended HTML, attributes, or event handlers.Dependency chain:
honois a transitive dependency via@modelcontextprotocol/sdk:@react-grab/mcp@0.1.29→@modelcontextprotocol/sdk@1.27.1→hono@4.12.14@modelcontextprotocol/sdk@1.29.0→hono@4.12.14Fix: Added Yarn resolutions in the root
package.jsonto force all instances ofhonoto resolve to^4.12.18, which includes fixes for multiple CVEs.References
Linear Issue: SOU-1068