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.3% (17th percentile of EPSS-scored CVEs). 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.3%CVSS: 4.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 7, 2026

Last Modified

September 9, 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 rangeFix by version rangeDependents
hono—
  • 3.8.0 up to 4.12.34: fixed in 4.12.34
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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-10-05 08:13 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-04 05:43 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 09:32 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 22:54 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 05:45 UTCEG score recompute
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 17:08 UTCEG score recompute
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-25 04:15 UTCEG score recompute
  15. 2026-09-23 17:54 UTCEPSS rescore
  16. 2026-09-23 13:46 UTCEG score recompute
  17. 2026-09-22 12:48 UTCEG score recompute
  18. 2026-09-21 21:09 UTCEPSS rescore
  19. 2026-09-21 12:03 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-20 10:54 UTCEG score recompute
  22. 2026-09-19 07:39 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-18 06:53 UTCEG score recompute
  25. 2026-09-17 06:09 UTCEG score recompute
Show 67 more
  1. 2026-09-16 14:08 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 04:29 UTCEG score recompute
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-14 03:13 UTCEG score recompute
  6. 2026-09-13 02:30 UTCEG score recompute
  7. 2026-09-12 15:02 UTCEPSS rescore
  8. 2026-09-12 01:47 UTCEG score recompute
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 01:03 UTCEG score recompute
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-09 06:00 UTCEG score recompute
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-07 17:43 UTCEG score recompute
  15. 2026-09-06 13:48 UTCEPSS rescore
  16. 2026-09-06 10:28 UTCEG score recompute
  17. 2026-09-05 09:45 UTCEG score recompute
  18. 2026-09-04 09:02 UTCEG score recompute
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-01 17:38 UTCEG score recompute
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-08-31 11:57 UTCEG score recompute
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 11:06 UTCEG score recompute
  25. 2026-08-30 01:22 UTCEPSS rescore
  26. 2026-08-29 10:22 UTCEG score recompute
  27. 2026-08-28 21:42 UTCEPSS rescore
  28. 2026-08-28 03:27 UTCEG score recompute
  29. 2026-08-27 02:28 UTCEG score recompute
  30. 2026-08-26 14:47 UTCEPSS rescore
  31. 2026-08-26 01:45 UTCEG score recompute
  32. 2026-08-25 13:49 UTCEPSS rescore
  33. 2026-08-25 01:02 UTCEG score recompute
  34. 2026-08-24 00:19 UTCEG score recompute
  35. 2026-08-23 00:19 UTCEPSS rescore
  36. 2026-08-22 23:36 UTCEG score recompute
  37. 2026-08-21 23:49 UTCEPSS rescore
  38. 2026-08-21 22:53 UTCEG score recompute
  39. 2026-08-20 22:56 UTCEPSS rescore
  40. 2026-08-19 21:26 UTCEG score recompute
  41. 2026-08-19 17:04 UTCEPSS rescore
  42. 2026-08-18 20:19 UTCEG score recompute
  43. 2026-08-18 13:49 UTCEPSS rescore
  44. 2026-08-18 13:49 UTCEPSS rescore
  45. 2026-08-17 19:33 UTCEG score recompute
  46. 2026-08-17 13:47 UTCEPSS rescore
  47. 2026-08-16 18:50 UTCEG score recompute
  48. 2026-08-16 14:56 UTCEPSS rescore
  49. 2026-08-16 14:56 UTCEPSS rescore
  50. 2026-08-16 02:15 UTCEPSS rescore
  51. 2026-08-15 18:07 UTCEG score recompute
  52. 2026-08-15 01:31 UTCEPSS rescore
  53. 2026-08-14 17:23 UTCEG score recompute
  54. 2026-08-13 22:00 UTCEPSS rescore
  55. 2026-08-12 15:56 UTCEG score recompute
  56. 2026-08-12 13:51 UTCEPSS rescore
  57. 2026-08-11 15:13 UTCEG score recompute
  58. 2026-08-11 00:00 UTCEPSS rescore
  59. 2026-08-10 14:30 UTCEG score recompute
  60. 2026-08-10 13:37 UTCEG score recompute
  61. 2026-08-09 20:55 UTCEG score recompute
  62. 2026-08-09 13:47 UTCEPSS rescore
  63. 2026-08-08 20:12 UTCEG score recompute
  64. 2026-08-08 16:37 UTCEPSS rescore
  65. 2026-08-07 19:28 UTCEG score recompute
  66. 2026-08-07 18:47 UTCEG score recompute
  67. 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 on August 7, 2026, with the most recent update on September 9, 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.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71850?
CVE-2026-71850 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71850?
A fix for CVE-2026-71850 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71850 are linked in the Vendor Advisories panel on this page.

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.