Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

hono: CORS Middleware reflects any Origin with credentials when origin defaults to the wildcard

CVE-2026-54290GHSA-88fw-hqm2-52qc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (hono 4.12.25), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm hono

    Affected
    < 4.12.25
    Fixed in
    4.12.25

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
EPSS
  • CVE-2026-54290: 0.33% estimated exploitation activity in the next 30 days; percentile 26.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-88fw-hqm2-52qc

  2. Revision 1 · created ·

    Published from osv record GHSA-88fw-hqm2-52qc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54290

Advisory: hono: CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard
IDs: CVE-2026-54290, GHSA-88fw-hqm2-52qc
Record: https://patchnext.com/advisories/cve-2026-54290 (revision 2, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hono 4.12.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm hono: affected < 4.12.25; fixed in 4.12.25

## Suggested inspection (read-only)
- `npm ls hono --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hono.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-88fw-hqm2-52qc (OSV record GHSA-88fw-hqm2-52qc lists affected ranges: npm hono >=0 <4.12.25 (fixed))
- Verified: https://github.com/advisories/GHSA-88fw-hqm2-52qc (GitHub-reviewed advisory GHSA-88fw-hqm2-52qc lists affected ranges: npm hono >=0 <4.12.25)

Commands are suggestions: review each one before running it.

Loading voting…