All reports
Critical

JWE is missing AES-GCM authentication tag validation in encrypted JWE

Affected versions

RubyGemsjwe
Affected versions
<= 1.1.0
Fixed version
1.1.1

Exploitation

CVE-2025-54887

Probability of exploitation in the next 30 days: 0.27%

FIRST EPSS · 2026-11-21

Description

Overview

The authentication tag of encrypted JWEs can be brute forced, which may result in loss of confidentiality for those JWEs and provide ways to craft arbitrary JWEs.

Impact
  • JWEs can be modified to decrypt to an arbitrary value

  • JWEs can be decrypted by observing parsing differences

  • The GCM internal GHASH key can be recovered

Am I Affected?

You are affected by this vulnerability even if you do not use an AES-GCM encryption algorithm for your JWEs.

Patches

The version 1.1.1 fixes the issue by adding the tag length check for the AES-GCM algorithm.

Important: As the GHASH key could have leaked, you must rotate the encryption keys after upgrading to version 1.1.1.

References

Félix Charette talk at NorthSec 2025 about the issue

Links

Credits

  • Sideni