ZeroDay Findings
Sign inSign up

Findings

CVE-2026-47673

Hono is a Web application framework that provides support for any JavaScript runtime.

Published May 28, 2026 · updated Oct 14, 2026 · hono hono

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-Bearer scheme identifier (such as Basic or Token) is authenticated identically to a correctly formed Bearer request. This vulnerability is fixed in 4.12.21.

Timeline

Detection, updates, and resolution for this record.

  1. May 28, 2026 · NIST NVD

    Detected

    Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-Bearer scheme identifier (such as Basi

  2. Oct 14, 2026 · NIST NVD

    Updated

    Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first position — proceeds to JWT verification. A request presenting a valid JWT under a non-Bearer scheme identifier (such as Basi

Affected

  • cpe hono/honoversion unspecified

Sources

  • CVE.orgCVE-2026-47673

    Official CVE identifier

    cve.org
  • FIRST EPSSCVE-2026-47673

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDCVE-2026-47673

    Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the jwt and jwk middlewares do not verify that the Authorization header value uses theBearer scheme. Any two-part header value — regardless of the scheme name in the first posi

    nvd.nist.gov

References