CVE-2026-44457 Details
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.18, Cache Middleware does not skip caching for responses that declare per-user variance via Vary: Authorization or Vary: Cookie. As a result, a response cached for one authenticated user may be served to subsequent requests from different users. This vulnerability is fixed in 4.12.18.
A cache leakage vulnerability has been identified in Hono versions prior to 4.12.18. The issue arises in the Cache Middleware, which fails to bypass caching for responses that indicate per-user variance through 'Vary: Authorization' or 'Vary: Cookie'. Consequently, a response cached for one authenticated user may be inadvertently served to other users. This vulnerability is particularly concerning for applications that use the Cache Middleware on endpoints delivering user-specific data, without also applying 'Cache-Control: private'.
Users can upgrade to Hono version 4.12.18 or later to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 18, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/honojs/hono/security/advisories/GHSA-p77w-8qqv-26rm | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-524 | Use of Cache Containing Sensitive Information | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| hono hono | < 4.12.18 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 13, 2026 | Initial Analysis | [email protected] |
| May 13, 2026 | New CVE Received | [email protected] |