Security readout for executives and security teams
Plain-English summary
This flaw affects Hono applications using vulnerable CORS middleware. A client-controlled request header could influence the server's Vary response header, which may confuse shared caches or proxies. The main business risk is inconsistent cross-origin behavior or cache pollution, not direct system takeover.
Executive priority
Treat as a moderate-priority dependency update for Hono-backed web services. Prioritize internet-facing apps and services behind shared caches or proxies, because business impact is configuration-dependent.
Technical view
Hono CORS middleware reflected the incoming Vary request header into responses when origin was not "*". Sources classify this as CWE-113 with CVSS v4 6.9. Impact centers on cache variation semantics and CORS consistency behind shared caches or proxies. The source bundle says fixed in 4.10.3.
Likely exposure
Exposure is most likely in web services using Hono CORS middleware on affected versions through 4.10.2, especially behind shared caches, CDNs, or reverse proxies.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The issue is remotely reachable and unauthenticated per CVSS, but impact depends on cache or proxy behavior and CORS configuration.
Researcher notes
Evidence is limited to advisory-level details. Focus validation on version presence, CORS middleware usage, non-wildcard origin settings, and intermediary cache behavior. Do not assume data disclosure or active exploitation without additional source evidence.
Mitigation direction
- Upgrade Hono to 4.10.3 or later where feasible.
- Review vendor advisory guidance before relying on compensating controls.
- Audit Hono CORS configurations where origin is not "*".
- Review shared cache, CDN, and proxy behavior for affected routes.
- Monitor Hono and CVE advisories for any revised remediation details.
Validation and detection
- Inventory applications and package locks for Hono versions through 4.10.2.
- Confirm whether affected applications use Hono CORS middleware.
- Identify affected routes served through CDNs, shared caches, or reverse proxies.
- Verify responses manage Vary server-side after upgrading.
- Run existing unit and regression tests for CORS and cache-sensitive routes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-113: 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 lookupCVE-2025-71381 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-q7jf-gf43-6x6p)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Hono - Vary Header Injection in CORS MiddlewareCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.