CVE-2026-71850

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.8
EG Score
4.8(medium)
EG Risk
22(Track)
EG Risk 22/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Patch available. Sources: github.
github Patch Available

`memo()` retains SSR output across requests, leading to cross-user data disclosure · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-f23p-vx2j-j53r

Vendor Advisories for CVE-2026-71850(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
hono4.12.34

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-19 21:26 UTCEG score recompute
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 20:19 UTCEG score recompute
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-17 19:33 UTCEG score recompute
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 18:50 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 02:15 UTCEPSS rescore
  13. 2026-08-15 18:07 UTCEG score recompute
  14. 2026-08-15 01:31 UTCEPSS rescore
  15. 2026-08-14 17:23 UTCEG score recompute
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 15:56 UTCEG score recompute
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 15:13 UTCEG score recompute
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-10 14:30 UTCEG score recompute
  22. 2026-08-10 13:37 UTCEG score recompute
  23. 2026-08-09 20:55 UTCEG score recompute
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-08 20:12 UTCEG score recompute
Show 4 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-07 19:28 UTCEG score recompute
  3. 2026-08-07 18:47 UTCEG score recompute
  4. 2026-08-07 18:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71850?
CVE-2026-71850 is a medium vulnerability published on August 7, 2026. 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…
When was CVE-2026-71850 disclosed?
CVE-2026-71850 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71850 actively exploited?
CVE-2026-71850 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-71850?
CVE-2026-71850 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-71850?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71850, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71850

Explore →

Is Your Infrastructure Affected by CVE-2026-71850?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.