CVE-2026-54290: hono CORS Middleware Reflects Any Origin Vulnerability

HIGH
Advisory Identifier: GHSA-88fw-hqm2-52qc
Share
CVSS 7.1
CWE-942
Published
Advisory Summary

CVE-2026-54290 is a HIGH (CVSS 7.1) cors middleware reflects any origin vulnerability (CWE-942: Permissive Cross-domain Security Policy with Untrusted Domains) affecting hono libraries in the npm ecosystem. The issue involves cors middleware reflects any origin with credentials when `origin` defaults to the wildcard. Remediation is available by upgrading affected packages to version 4.12.25.

CVE-2026-54290 at a Glance

CVE Identifier CVE-2026-54290
GHSA Identifier GHSA-88fw-hqm2-52qc
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-942: Permissive Cross-domain Security Policy with Untrusted Domains
Affected Product hono
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-54290

To remediate this vulnerability, upgrade all affected hono dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

hono fixed: 4.12.25 
npm install hono@4.12.25
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls hono

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-54290, inspect your project dependencies using npm:

npm ls hono

Analyze the terminal output to locate any version of hono in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.12.25), your application is affected.

Note: The npm ls hono command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-942: Permissive Cross-domain Security Policy with Untrusted Domains, where the product uses a web-client protection mechanism such as a content security policy (csp) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate. In hono, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. ### Details The spec forbids `Access-Control-Allow-Origin: *` with credentials and browsers reject it, so this configuration used to fail closed. In affected versions the middleware reflects the request `Origin` instead, so it now succeeds for every origin, including `null`. The preflight also echoes the requested headers back, approving non-simple credentialed requests too. This issue arises when an application enables `credentials: true` and leaves `origin` unset or set to the wildcard. ### Impact Any third-party page a logged-in user visits can read the application's cookie-authenticated endpoints and perform credentialed state-changing requests. This affects applications that enable credentialed CORS without restricting `origin`.

CVE-2026-54290 Affected hono Versions

1 component(s)
Fixed Versions:
4.12.25
Product / Package Ecosystem Affected Versions Fixed Version
hono
npm/hono
npm
< 4.12.25
4.12.25

References

GitHub Advisory / Wiki ADVISORY
https://github.com/honojs/hono/security/advisories/GHSA-88fw-hqm2-52qc
NVD — CVE-2026-54290 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-54290
hono Source Repository REPOSITORY
https://github.com/honojs/hono

Frequently Asked Questions

What is CVE-2026-54290?
CVE-2026-54290 is a security vulnerability in hono involving CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard under CWE-942: Permissive Cross-domain Security Policy with Untrusted Domains.
Which hono versions are affected?
Affected versions include releases prior to 4.12.25 across affected packages: hono.
What version fixes CVE-2026-54290?
Upgrading to 4.12.25 (or the latest patched release for your respective branch) resolves the vulnerability.
Is hono affected?
Yes, hono is affected in releases prior to 4.12.25. Upgrade your dependency to 4.12.25 or later.
What is the CVSS score of CVE-2026-54290?
CVE-2026-54290 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2026-54290?
CVE-2026-54290 is classified under CWE-942: Permissive Cross-domain Security Policy with Untrusted Domains (The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.).
How can I check npm dependencies for CVE-2026-54290?
Run the dependency tree command: 'npm ls hono'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-88fw-hqm2-52qc",
  "modified" : "2026-07-21T15:27:03Z",
  "published" : "2026-06-16T14:15:39Z",
  "aliases" : [ "CVE-2026-54290" ],
  "summary" : "hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard",
  "details" : "### Summary\n\nWith `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.\n\n### Details\n\nThe spec forbids `Access-Control-Allow-Origin: *` with credentials and browsers reject it, so this configuration used to fail closed. In affected versions the middleware reflects the request `Origin` instead, so it now succeeds for every origin, including `null`. The preflight also echoes the requested headers back, approving non-simple credentialed requests too.\n\nThis issue arises when an application enables `credentials: true` and leaves `origin` unset or set to the wildcard.\n\n### Impact\n\nAny third-party page a logged-in user visits can read the application's cookie-authenticated endpoints and perform credentialed state-changing requests. This affects applications that enable credentialed CORS without restricting `origin`.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "hono"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.12.25"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/honojs/hono/security/advisories/GHSA-88fw-hqm2-52qc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54290"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/honojs/hono"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-942" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-16T14:15:39Z",
    "nvd_published_at" : "2026-06-22T18:16:47Z"
  }
}