npm
CVE-2026-71850
Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosure
- Severity
- Medium 4.8
- Published
- 7 Aug 2026
- Last changed
- 10 Sept 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 4.12.34
- Exploit chance
- 0.3% in the next 30 daysHigher than 19% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-488
- Attack
- Over the network · Only under certain conditions · Needs a user account · Needs someone to click or open something
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N- Also known as
- GHSA-f23p-vx2j-j53r
- Sources
- OSV.dev and GitHub
Description
memo() from hono/jsx retains the result of a server-side render and reuses it for later renders with comparator-equal props. Request-scoped values read inside the component take no part in that comparison, so a response can contain HTML rendered for another user's request.
Components wrapped with memo() are compared by props alone. Values read implicitly during rendering do not participate: JSX Context through createContext() and useContext(), useRequestContext() from hono/jsx-renderer, and getContext() from hono/context-storage. The retained result lives as long as the wrapped component, so it outlives the request that produced it.
Per-request context isolation is not what fails: the current request's values are established correctly, but the memoized component is skipped before anything reads them.
This issue arises when a component wrapped in memo() obtains user- or request-specific data from an ambient context instead of through props.
Affected software
| Software | Affected versions |
|---|---|
hononpm · osv:npm:hono |
|
About hono
- Weekly downloads (npm)
- 108,805,821npm, 16 Nov 2026
Vulnerabilities in hono
- In our list
- 26
- Published in the last 12 months
- 26
- Critical, last 12 months
- 0
- High, last 12 months
- 1
- Known exploited
- 0
- CVE-2026-109955Hono: `serveStatic` decodes the request path a second time, leading to bypass of middleware on static pathsMedium 5.3 20 Oct 2026
- CVE-2026-93981hono/jsx renders plain strings unescaped in boundary components, leading to XSSMedium 4.7 30 Sept 2026
- CVE-2026-84365Hono: Incomplete fix for CVE-2026-39408: `toSSG()` still writes files outside the output directoryMedium 6.5 8 Sept 2026
- CVE-2026-84364Hono: Unbounded dot-notation nesting in `parseBody()` can cause memory exhaustionMedium 5.3 8 Sept 2026
- CVE-2026-84363Hono: Query parser reads parameters after the URL fragment, causing cache-key and proxy interpretation differentialsMedium 5.9 8 Sept 2026
- CVE-2026-71849Hono: Proxy Helper does not remove response headers listed in the `Connection` headerLow 3.7 7 Aug 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-71850
- GitHub Advisory Database https://github.com/advisories/GHSA-f23p-vx2j-j53r