LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24472: Hono cache middleware ignores "Cache-Control: private" leading to Web Cache Deception

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to version 4.11.7, 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. Version 4.11.7 has a patch for the issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24472 affects Hono’s cache middleware before version 4.11.7. It may cache pages that are meant to stay private, including authenticated responses, because it ignores headers such as “Cache-Control: private” and “no-store.” This can expose sensitive information to other users through caching behavior.

Executive priority

Treat as a targeted confidentiality issue. Prioritize internet-facing or customer-facing Hono applications that cache authenticated content. Upgrade during the next security maintenance window, faster if sensitive user data could be cached.

Technical view

Hono cache middleware before 4.11.7 improperly handles HTTP cache-control directives, creating an information disclosure risk. The issue is mapped to CWE-524 and CWE-613, with CVSS 3.1 score 5.3. The vendor states 4.11.7 patches the issue. Scope is Hono applications using the affected cache middleware.

Likely exposure

Exposure is likely in JavaScript applications using hono versions before 4.11.7 and its cache middleware on routes returning private, authenticated, or user-specific responses.

Exploitation context

No public active exploitation is indicated in the provided sources, and this CVE is not listed as KEV. Risk depends on application routing and cache placement. The main concern is unintended disclosure through cached responses, not system takeover.

Researcher notes

The public record identifies the vulnerable component and patched version but does not provide broad exploitation evidence. Focus triage on middleware usage and response sensitivity, not just package presence. The commit and advisory are the best sources for implementation details.

Mitigation direction

  • Upgrade hono to version 4.11.7 or later.
  • Identify applications using Hono cache middleware before 4.11.7.
  • Avoid affected cache middleware on authenticated or private-response routes until upgraded.
  • Review the GitHub advisory and release notes for vendor guidance.

Validation and detection

  • Check dependency manifests and lockfiles for hono versions below 4.11.7.
  • Review route configuration for Hono cache middleware on private or authenticated endpoints.
  • Confirm upgraded deployments use hono 4.11.7 or later.
  • Verify private/no-store responses are not cached after remediation.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-524: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-613: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24472 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-24472Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
honojshono< 4.11.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-524 · source CWE mapping

Use of Cache Containing Sensitive Information

Use of Cache Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.