CVE-2026-93981: Hono Package XSS Vulnerability in JSX Rendering

hono Updated 01 Oct 2026

Summary

30/09/2026
Yes i
Moderate
4.7

CVE-2026-93981: hono/jsx renders plain strings unescaped in boundary components, leading to XSS. Affects hono versions < 4.13.7. Fixed in 4.13.7. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Hono is a lightweight web framework designed for building web applications and APIs with a focus on performance and simplicity. It utilizes JSX for rendering components, allowing developers to create dynamic user interfaces. However, a recent vulnerability has been identified in the way Hono handles plain strings in certain rendering contexts, which can lead to cross-site scripting (XSS) attacks.

Vulnerability Detail

The vulnerability arises from the fact that Hono's JSX does not properly escape plain strings when they are rendered as children in specific components such as Suspense, ErrorBoundary, or Context.Provider. This oversight allows an attacker to inject arbitrary HTML into the server-rendered page if they control the string being rendered. The affected paths treat the input as already-escaped HTML, leading to potential XSS under the application's origin. This issue is particularly concerning for applications that render untrusted strings directly during server-side rendering.

How To Fix

Latest published version: 4.13.13 as of 23 Oct 2026

npm install hono@4.13.13

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.13.7

This is the first release that contains the fix.

npm install hono@4.13.7

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, avoid rendering plain strings directly in the affected components. Instead, wrap strings in a safe HTML element or use the raw() or html helper functions provided by Hono to ensure proper escaping.

Conclusion

The CVE-2026-93981 vulnerability in the Hono package poses a significant risk due to improper handling of plain strings in JSX rendering, leading to potential XSS attacks. It is crucial for developers using Hono to update to version 4.13.7 or later to mitigate this risk. Additionally, implementing workarounds can provide temporary relief while ensuring application security.

See every vulnerability recorded for hono →

Share this vulnerability

FAQ

CVE-2026-93981 is a vulnerability in the Hono package that allows for cross-site scripting (XSS) due to improper handling of plain strings in JSX rendering.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor for open-source vulnerabilities without requiring signup.

An attacker could inject malicious HTML into your application, potentially leading to data theft, session hijacking, or other malicious activities.

Yes, the vulnerability has been patched in version 4.13.7 of the Hono package. Updating to this version will resolve the issue.

The CVSS score for this vulnerability is 4.7, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for hono.

How To Fix

Latest published version: 4.13.13 as of 23 Oct 2026

npm install hono@4.13.13

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.13.7

This is the first release that contains the fix.

npm install hono@4.13.7

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback