Hono vulnerable to Vary Header Injection leading to potential CORS Bypass
What fixes it
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
Summary
A flaw in the CORS middleware allowed request Vary headers to be reflected into the response, enabling attacker-controlled Vary values and potentially affecting cache behavior.
Details
The middleware previously copied the Vary header from the request when origin was not set to "*". Since Vary is a response header that should only be managed by the server, this could allow an attacker to influence caching behavior or cause inconsistent CORS handling.
Most environments will see impact only when shared caches or proxies rely on the Vary header. The practical effect varies by configuration.
Impact
May cause cache key pollution and inconsistent CORS enforcement in certain setups. No direct confidentiality, integrity, or availability impact in default configurations.
Resolution
Update to the latest patched release. The CORS middleware has been corrected to handle Vary exclusively as a response header.
Text from GitHub Advisory Database
Affected versions 4
- hono, npm< 4.10.3GitHub
- Honoaffected: all versions before 4.10.2CVE List
- Honounaffected: 4.10.2CVE List
- hono, npmfrom first release, fixed in 4.10.3OSV
References 5
- github.com/honojs/hono/commit/d9b8b4b73b4f997994f2764013207365fe711282Fixvia GitHub
- github.com/honojs/hono/security/advisories/GHSA-q7jf-gf43-6x6pAdvisoryvia CVE List
- vulncheck.com/advisories/hono-vary-header-injection-in-cors-middlewareAdvisoryvia CVE List
- github.com/advisories/GHSA-q7jf-gf43-6x6pAdvisoryvia GitHub
- nvd.nist.gov/vuln/detail/CVE-2025-71381Referencevia GitHub