CVE-2026-54290: CWE-942: Permissive Cross-domain Policy with Untrusted Domains in honojs hono
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.25, with credentials: true and no explicit origin (the default wildcard), the CORS Middleware reflects the request's Origin and sends Access-Control-Allow-Credentials: true. Any site can then make credentialed cross-origin requests and read the responses, exposing cookie-authenticated endpoints to arbitrary origins. This vulnerability is fixed in 4.12.25.
AI Analysis
Technical Summary
CVE-2026-54290 describes a permissive cross-domain policy vulnerability (CWE-942) in the honojs hono framework before version 4.12.25. When the CORS middleware is configured with credentials: true and no explicit origin (defaulting to a wildcard), it reflects the request's Origin header and sends Access-Control-Allow-Credentials: true. This allows any external site to perform credentialed cross-origin requests and access sensitive responses, exposing cookie-authenticated endpoints to untrusted origins. The vulnerability is resolved in hono version 4.12.25.
Potential Impact
The vulnerability allows arbitrary external origins to make credentialed cross-origin requests and read responses from the vulnerable hono application, potentially exposing sensitive user data protected by cookies. This can lead to unauthorized data disclosure. The CVSS score is 7.1 (high severity), indicating a network attack vector with low complexity, no privileges required, user interaction needed, and high confidentiality impact.
Mitigation Recommendations
Upgrade hono to version 4.12.25 or later, where this vulnerability is fixed. There is no official remediation level stated beyond this fix. Patch status is confirmed by the version update. Until patched, avoid using credentials: true with the default wildcard origin in CORS middleware configurations.
CVE-2026-54290: CWE-942: Permissive Cross-domain Policy with Untrusted Domains in honojs hono
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.25, with credentials: true and no explicit origin (the default wildcard), the CORS Middleware reflects the request's Origin and sends Access-Control-Allow-Credentials: true. Any site can then make credentialed cross-origin requests and read the responses, exposing cookie-authenticated endpoints to arbitrary origins. This vulnerability is fixed in 4.12.25.
CVSS v3.1
Score 7.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-54290 describes a permissive cross-domain policy vulnerability (CWE-942) in the honojs hono framework before version 4.12.25. When the CORS middleware is configured with credentials: true and no explicit origin (defaulting to a wildcard), it reflects the request's Origin header and sends Access-Control-Allow-Credentials: true. This allows any external site to perform credentialed cross-origin requests and access sensitive responses, exposing cookie-authenticated endpoints to untrusted origins. The vulnerability is resolved in hono version 4.12.25.
Potential Impact
The vulnerability allows arbitrary external origins to make credentialed cross-origin requests and read responses from the vulnerable hono application, potentially exposing sensitive user data protected by cookies. This can lead to unauthorized data disclosure. The CVSS score is 7.1 (high severity), indicating a network attack vector with low complexity, no privileges required, user interaction needed, and high confidentiality impact.
Mitigation Recommendations
Upgrade hono to version 4.12.25 or later, where this vulnerability is fixed. There is no official remediation level stated beyond this fix. Patch status is confirmed by the version update. Until patched, avoid using credentials: true with the default wildcard origin in CORS middleware configurations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-12T17:46:37.293Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a39735ceed863c81e3962ad
Added to database: 06/22/2026, 17:39:40 UTC
Last enriched: 06/22/2026, 17:54:13 UTC
Last updated: 06/23/2026, 02:52:21 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.