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.
Metrics
Affected Vendors & Products
References
History
Tue, 12 Aug 2025 08:00:00 +0000
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 |
Fri, 08 Aug 2025 17:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Fri, 08 Aug 2025 00:45:00 +0000
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
|

Status: PUBLISHED
Assigner: GitHub_M
Published: 2025-08-08T00:06:20.021Z
Updated: 2025-08-08T16:43:15.548Z
Reserved: 2025-07-31T17:23:33.476Z
Link: CVE-2025-54887

Updated: 2025-08-08T16:43:10.387Z

Status : Awaiting Analysis
Published: 2025-08-08T01:15:25.287
Modified: 2025-08-08T20:30:18.180
Link: CVE-2025-54887

No data.