jwe: Missing AES-GCM authentication tag validation in encrypted JWEs
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| jwt | ruby-jwe | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Ruby-jwe Project | Ruby-jwe | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-23966 | JWE is missing AES-GCM authentication tag validation in encrypted JWE |
Github GHSA |
GHSA-c7p4-hx26-pr73 | JWE is missing AES-GCM authentication tag validation in encrypted JWE |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.268% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ruby-jwe Project
Ruby-jwe Project ruby-jwe |
|
| Vendors & Products |
Ruby-jwe Project
Ruby-jwe Project ruby-jwe |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | jwe is a Ruby implementation of the RFC 7516 JSON Web Encryption (JWE) standard. In versions 1.1.0 and below, authentication tags of encrypted JWEs can be brute forced, which may result in loss of confidentiality for those JWEs and provide ways to craft arbitrary JWEs. This puts users at risk because JWEs can be modified to decrypt to an arbitrary value, decrypted by observing parsing differences and the GCM internal GHASH key can be recovered. Users are affected by this vulnerability even if they do not use an AES-GCM encryption algorithm for their JWEs. As the GHASH key may have been leaked, users must rotate the encryption keys after upgrading. This issue is fixed in version 1.1.1. | |
| Title | jwe: Missing AES-GCM authentication tag validation in encrypted JWEs | |
| Weaknesses | CWE-354 | |
| References |
| |
| Metrics |
cvssV3_1
|