Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-71850— Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosure

Quick assessment

Affected
honojs hono
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

honojs Hono是honojs组织开源的一个轻量级的Web服务器框架。 Hono 3.8.0版本至4.12.34之前版本存在会话机制问题漏洞,该漏洞源于memo()函数保留服务端渲染结果并在后续渲染中重用,未将请求作用域值纳入比较,可能导致响应中包含其他用户请求的HTML,从而泄露其他用户的账户或资料数据、CSRF令牌等请求作用域敏感信息,或将角色特定内容暴露给不应接收的用户。

CVSS 4.8 · Medium EPSS 0.27% · P17

Affected Version Matrix 1

VendorProduct Version RangeStatus
honojs hono >= 3.8.0, < 4.12.34 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-71850

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosure
Source: CVE Program / CVE List V5
Vulnerability Description
Hono is a Web application framework that provides support for any JavaScript runtime. From 3.8.0 to 4.12.33, memo() from hono/jsx retains the result of a server side render and reuses it for later renders with comparator equal props, and 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, such as JSX Context through createContext() and useContext(), useRequestContext() from hono/jsx-renderer, and getContext() from hono/context-storage, do not participate, and the retained result lives as long as the wrapped component, so it outlives the request that produced it. A user may receive a response containing HTML rendered for another user when both render the same memoized component with comparator equal props on the same warm instance, which may disclose another user's account or profile data, disclose request scoped secrets embedded in HTML such as CSRF tokens, or expose role specific content to users who should not receive it. This issue is fixed in version 4.12.34.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
对错误会话暴露数据元素
Source: CVE Program / CVE List V5
Vulnerability Title
Hono 会话机制问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
honojs Hono是honojs组织开源的一个轻量级的Web服务器框架。 Hono 3.8.0版本至4.12.34之前版本存在会话机制问题漏洞,该漏洞源于memo()函数保留服务端渲染结果并在后续渲染中重用,未将请求作用域值纳入比较,可能导致响应中包含其他用户请求的HTML,从而泄露其他用户的账户或资料数据、CSRF令牌等请求作用域敏感信息,或将角色特定内容暴露给不应接收的用户。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
honojs hono >= 3.8.0, < 4.12.34 -

II. Public POCs for CVE-2026-71850

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-71850

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-71850 (1)

Same Patch Batch · honojs · 2026-08-07 · 4 CVEs total

CVE-2026-69207 5.3 MEDIUM Hono: ReDoS in CORS middleware via Access-Control-Request-Headers
CVE-2026-71848 5.3 MEDIUM Hono: Algorithmic Complexity DoS in Language Middleware
CVE-2026-71849 3.7 LOW Hono: Proxy Helper does not remove response headers listed in the `Connection` header

IV. Related Vulnerabilities

V. Comments for CVE-2026-71850

No comments yet


Leave a comment