Approved changes feed: RSS · Atom
cpe:2.3:a:jwt:ruby-jwe:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Jwt (baeda3dc-0133-5972-a564-7885f79f5452) |
|---|---|
| Product | Ruby Jwe (4c23a09c-3f52-5bdc-8648-c51fff083f65) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-54887 |
vulnerable | 2026-06-08 07:33:13.533214 |
jwe: Missing AES-GCM authentication tag validation in encrypted JWEs
CRITICAL (9.1)
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.
Published: 2025-08-08T00:06:20.021Z
Updated: 2025-08-08T16:43:15.548Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.