Hono cache middleware ignores "Cache-Control: private" leading to Web Cache Deception
CVE-2026-24472GHSA-6wqw-2p9w-4vw4
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (hono 4.11.7), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm hono
- Affected
- < 4.11.7
- Fixed in
- 4.11.7
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-6wqw-2p9w-4vw4 lists affected ranges: npm hono >=0 <4.11.7 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6wqw-2p9w-4vw4 lists affected ranges: npm hono >=0 <4.11.7
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-24472: 0.52% estimated exploitation activity in the next 30 days; percentile 44.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Cache Middleware contains an information disclosure vulnerability caused by improper handling of HTTP cache control directives. The middleware does not respect standard cache control headers such as Cache-Control: private or Cache-Control: no-store, which may result in private or authenticated responses being cached and subsequently exposed to unauthorized users. Details The vulnerability exists in the cache decision logic of Cache Middleware. When determining whether a response should be cached, the middleware does not take HTTP cache control semantics into account and may cache responses that are explicitly marked as private by the application. While some runtimes, such as Cloudflare Workers, enforce cache control restrictions at the platform level, other runtimes including Deno, Bun, and Node.js rely on the middleware’s behavior. As a result, applications running on these runtimes may unintentionally cache sensitive responses. Impact This issue can lead to Web Cache…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-6wqw-2p9w-4vw4
- Revision 1 · created ·
Published from osv record GHSA-6wqw-2p9w-4vw4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-24472 Advisory: Hono cache middleware ignores "Cache-Control: private" leading to Web Cache Deception IDs: CVE-2026-24472, GHSA-6wqw-2p9w-4vw4 Record: https://patchnext.com/advisories/cve-2026-24472 (revision 2, source checked 26 Oct 2026, 12:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: hono 4.11.7. A vendor fix does not mean a deployment is fixed. ## Affected components - npm hono: affected < 4.11.7; fixed in 4.11.7 ## Suggested inspection (read-only) - `npm ls hono --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on hono. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-6wqw-2p9w-4vw4 (OSV record GHSA-6wqw-2p9w-4vw4 lists affected ranges: npm hono >=0 <4.11.7 (fixed)) - Verified: https://github.com/advisories/GHSA-6wqw-2p9w-4vw4 (GitHub-reviewed advisory GHSA-6wqw-2p9w-4vw4 lists affected ranges: npm hono >=0 <4.11.7) Commands are suggestions: review each one before running it.
Loading voting…