CVE-2025-54887

jwe: Missing AES-GCM authentication tag validation in encrypted JWEs

Published Aug 8, 2025 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2025-23966 JWE is missing AES-GCM authentication tag validation in encrypted JWE
Github GHSA Github GHSA GHSA-c7p4-hx26-pr73 JWE is missing AES-GCM authentication tag validation in encrypted JWE
History
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

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

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

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 8, 2025, 4:43 PM
Reserved
Jul 31, 2025, 5:23 PM
Status
Deferred
Published
Aug 8, 2025, 1:15 AM
Modified
Jun 17, 2026, 9:40 AM