honojs hono up to 4.11.3 JWK/JWKS signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in honojs hono up to 4.11.3. Affected by this issue is some unknown functionality of the component JWK/JWKS. This manipulation causes signature verification. This vulnerability is tracked as CVE-2026-22818. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical was found in honojs hono up to 4.11.3. Affected by this vulnerability is an unknown functionality of the component JWK/JWKS. The manipulation with an unknown input leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.11.4, there is a flaw in Hono’s JWK/JWKS JWT verification middleware allowed the algorithm specified in the JWT header to influence signature verification when the selected JWK did not explicitly define an algorithm. This could enable JWT algorithm confusion and, in certain configurations, allow forged tokens to be accepted. The JWK/JWKS JWT verification middleware has been updated to require an explicit allowlist of asymmetric algorithms when verifying tokens. The middleware no longer derives the verification algorithm from untrusted JWT header values. This vulnerability is fixed in 4.11.4.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-22818 since 01/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
Upgrading to version 4.11.4 eliminates this vulnerability. Applying the patch 190f6e28e2ca85ce3d1f2f54db1310f5f3eab134 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0328). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- IBM App Connect Enterprise
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/honojs/hono/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
CNA Base Score: 8.2
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: hono 4.11.4
Patch: 190f6e28e2ca85ce3d1f2f54db1310f5f3eab134
Timeline
01/09/2026 CVE reserved01/14/2026 Advisory disclosed
01/14/2026 VulDB entry created
02/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-3vhc-576x-3qv4
Status: Confirmed
CVE: CVE-2026-22818 (🔒)
GCVE (CVE): GCVE-0-2026-22818
GCVE (VulDB): GCVE-100-340957
CERT Bund: WID-SEC-2026-0328 - IBM App Connect Enterprise Certified Container: Mehrere Schwachstellen
Entry
Created: 01/14/2026 08:19Updated: 02/06/2026 12:59
Changes: 01/14/2026 08:19 (66), 01/21/2026 05:37 (11), 02/06/2026 12:59 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.