Security readout for executives and security teams
Plain-English summary
Hono applications using vulnerable JWT verification middleware may accept forged login tokens in some configurations. This can let an unauthenticated attacker bypass authentication and act as another user or trusted caller. The issue is fixed in Hono 4.11.4.
Executive priority
Treat as high priority for products using Hono-based authentication. Patch or reconfigure quickly because successful abuse can bypass login controls without user interaction. Focus first on public APIs, customer portals, and service-to-service authentication paths.
Technical view
Before Hono 4.11.4, JWK/JWKS JWT middleware could let the untrusted JWT header alg influence signature verification when the selected JWK did not explicitly define an algorithm. This creates JWT algorithm confusion, mapped to CWE-347, with CVSS 8.2.
Likely exposure
Exposure is most likely in JavaScript services using hono versions before 4.11.4 with Hono JWK/JWKS JWT verification middleware, especially where JWKs lack an explicit alg. Applications not using this middleware or already on 4.11.4 are less likely exposed.
Exploitation context
The source bundle does not show active exploitation, and this CVE is not marked KEV. Exploitation would require a vulnerable Hono version and affected JWT verification configuration. Impact is primarily authentication bypass and token forgery, with high integrity risk.
Researcher notes
The advisory states the fix requires explicit alg configuration so verification is not derived from JWT header values. The provided commit is the relevant code-change reference. Evidence is limited to vendor/CVE materials; no public exploitation evidence is included.
Mitigation direction
- Upgrade Hono to version 4.11.4 or later.
- Set the JWT middleware alg option explicitly as vendor guidance requires.
- Review JWK/JWKS entries for explicit algorithm declarations.
- Prioritize internet-facing APIs and authentication gateways first.
Validation and detection
- Inventory services using the hono package.
- Identify versions older than 4.11.4.
- Check whether JWK/JWKS JWT middleware is used.
- Review middleware configuration for explicit alg settings.
- Confirm the selected JWKs define expected algorithms.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22817 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N3.94.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/honojs/hono/security/advisories/GHSA-f67f-6cw9-8mq4CVE reference · x_refsource_CONFIRM
- https://github.com/honojs/hono/commit/cc0aa7ae327ed84cc391d29086dec2a3e44e7a1fCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.