All vulnerabilities

npm

CVE-2026-59896

hono/jsx does not isolate context per request, leading to cross-request data disclosure

Severity
Medium 6.5
Published
21 Jul 2026
Last changed
10 Sept 2026
Added to UpHeron
22 Oct 2026
Fixed in
4.12.27
Exploit chance
0.3% in the next 30 daysHigher than 23% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Race condition (CWE-362)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read data · Change some data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Also known as
GHSA-hvrm-45r6-mjfj
Sources
OSV.dev and GitHub

Description

hono/jsx did not isolate context values per request during server-side rendering. While an async component was suspended on await, its provided context value stayed observable to other requests rendering concurrently, so useContext() could return a value from a different in-flight request.

During server-side rendering, context values were kept in a process-wide structure rather than scoped to each request's render. While an async component awaited, another request entering the same provider could observe or replace the value; when the first render resumed, it could read the other request's context.

This affects the usual ways request-scoped data is passed through a server-rendered JSX tree:

  • createContext() / useContext()
  • the jsxRenderer middleware and useRequestContext()

It arises only when context is read after an await inside an async component while requests render concurrently.

From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

Affected software

SoftwareAffected versions
hononpm · osv:npm:hono
  • From 4.11.8 before 4.12.27

About hono

Weekly downloads (npm)
108,805,821npm, 16 Nov 2026

References