Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-24771

Hono vulnerable to XSS through ErrorBoundary component

Overview

Published
27 Jan 2026
Modified
17 Jun 2026
Medium CVE
1 Registry packages
5 OS packages
3 Linux distributions
Yes Fix available

Description

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to version 4.11.7, a Cross-Site Scripting (XSS) vulnerability exists in the ErrorBoundary component of the hono/jsx library. Under certain usage patterns, untrusted user-controlled strings may be rendered as raw HTML, allowing arbitrary script execution in the victim's browser. Version 4.11.7 patches the issue.

Source: OX vulnerability database

Severity

4.7 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

Weakness: CWE-79

Affected packages · 1

Packages affected by CVE-2026-24771
EcosystemPackageVulnerableFixed in
npm hono <4.11.7 4.11.7

Open a package to see all its vulnerabilities.

Operating systems · 7 fixes

chainguard 1 release · 4 packages

not affected 1 fixed 3
hono librechat langfuse-fips-3 langfuse-3
chainguard fixes for CVE-2026-24771
ReleasePackageFixed in
hono not affected
librechat 0.8.2-r1
langfuse-fips-3 3.152.0-r0
langfuse-3 3.153.0-r0

minimos 1 release · 2 packages

fixed 2
mcp-filesystem trigger-dev
minimos fixes for CVE-2026-24771
ReleasePackageFixed in
mcp-filesystem 2026.6.16-r0
trigger-dev 4.5.4-r0

wolfi 1 release · 1 package

fixed 1
langfuse-3
wolfi fixes for CVE-2026-24771
ReleasePackageFixed in
langfuse-3 3.153.0-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.