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-71850

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

Overview

Published
7 Aug 2026
Modified
24 Oct 2026
Medium CVE
3 Registry packages
25 OS packages
3 Linux distributions
Yes Fix available

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: OX vulnerability database

Severity

4.8 · MEDIUM

CVSS 3.1 base score, scored by NVD.

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

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

Weakness: CWE-488

Affected packages · 3

Packages affected by CVE-2026-71850
EcosystemPackageVulnerableFixed in
npm hono >=3.8.0, <4.12.34 4.12.34
Seal npm @seal-security/hono >=4.12.32-sp1, <4.12.32-sp999 4.12.32-sp999
Seal npm hono >=4.12.32-sp0, <4.12.32-sp999 4.12.32-sp999

Open a package to see all its vulnerabilities.

Operating systems · 24 fixes

chainguard 1 release · 14 packages

fixed 14
supabase-fips supabase commercial-gitlab-rails-ee-19-1 commercial-gitlab-rails-ee-fips-19-1 commercial-gitlab-rails-ee-19-2 commercial-gitlab-rails-ee-19-3 +8
chainguard fixes for CVE-2026-71850
ReleasePackageFixed in
supabase-fips 1.26.08-r3
supabase 1.26.08-r5
commercial-gitlab-rails-ee-19-1 19.1.7-r3
commercial-gitlab-rails-ee-fips-19-1 19.1.9-r0
commercial-gitlab-rails-ee-19-2 +1 19.2.7-r1
commercial-gitlab-rails-ee-19-3 +1 19.3.3-r1

8 more rows

minimos 1 release · 9 packages

fixed 9
n8n openclaw mcp-memory mcp-mongodb langfuse-4 trigger-dev +3
minimos fixes for CVE-2026-71850
ReleasePackageFixed in
n8n 2.36.6-r0
openclaw 2026.8.1-r0
mcp-memory 2026.8.18-r0
mcp-mongodb 3.1.0-r0
langfuse-4 4.30.0-r0
trigger-dev 4.5.12-r0

3 more rows

wolfi 1 release · 1 package

fixed 1
langfuse-3
wolfi fixes for CVE-2026-71850
ReleasePackageFixed in
langfuse-3 3.225.7-r6

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.