GHSA-6vvh-pxr4-25r7 Impact The experimental `Chacha20Poly1305` key-encryption algorithm generates the 16-byte Poly1305 authentication tag during `encryptKey
An attacker can tamper with encrypted JWT keys without detection because the authentication tag is discarded, bypassing integrity checks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-6vvh-pxr4-25r7?
GHSA-6vvh-pxr4-25r7 is a vulnerability in web-token/jwt-experimental, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Impact
The experimental Chacha20Poly1305 key-encryption algorithm generates the 16-byte Poly1305 authentication tag during encryptKey() but discards it: the tag is never written to the header and therefore never reaches the wire. On the receiving side, decryptKey() calls openssl_decrypt('chacha20-poly1305', ...) without the tag argument, which makes OpenSSL skip authentication entirely.
As a result the AEAD construction is silently degraded to unauthenticated ChaCha20: a tampered encrypted CEK is accepted, and because ChaCha20 is a stream cipher, a single-byte change in the ciphertext propagates as a single-byte change in the recovered CEK with no integrity check (CWE-353 / CWE-347). An attacker on the token path can manipulate the wrapped key without detection.
Affected configurations
Applications that register Jose\Experimental\KeyEncryption\Chacha20Poly1305 (package web-token/jwt-experimental) as a JWE alg.
Patches
encryptKey() now publishes the Poly1305 tag as the base64url tag header parameter (and asserts it is 16 bytes). decryptKey() requires the tag header, validates its length, and passes it to openssl_decrypt() so the tag is actually verified, in line with RFC 7539 / RFC 8439. Tampering now results in a decryption failure.
> Note: this changes the wire format of tokens produced with this experimental algorithm (a tag header is now emitted and required).
Workarounds
Do not use the experimental Chacha20Poly1305 key-encryption algorithm for untrusted input until upgraded.
References
- RFC 7539 / RFC 8439 (ChaCha20-Poly1305 AEAD)
- CWE-353: Missing Support for Integrity Check
Résolution
Un correctif a été préparé sur une branche dédiée basée sur 3.4.x, avec des tests anti-régression dédiés (fork privé temporaire de cette advisory, PR #1).
ChaCha20-Poly1305 — le tag d'authentification Poly1305 est désormais publié dans le header au chiffrement et vérifié au déchiffrement (RFC 7539), rétablissant l'intégrité AEAD.
Validation : php -l OK, PHPUnit vert, aucune nouvelle erreur PHPStan introduite (différentiel nul vs 3.4.x), aucun commentaire ajouté dans le code source. Après merge, cascade prévue 3.4.x → 4.0.x → 4.1.x.
Which versions are affected by GHSA-6vvh-pxr4-25r7?
8 open source packages ship an affected version, including web-token/jwt-experimental and web-token/jwt-library.
| Package | Affected | Fixed in |
|---|---|---|
web-token/jwt-experimental Packagist | All versions to 4.1.6 | None |
web-token/jwt-experimental Packagist | All versions to 4.1.6 | None |
web-token/jwt-library Packagist | All versions | 3.4.10 |
web-token/jwt-library Packagist | All versions | 3.4.10 |
web-token/jwt-library Packagist | From 4.0.0 | 4.0.7 |
web-token/jwt-library Packagist | From 4.0.0 | 4.0.7 |
2 more packages
web-token/jwt-library Packagist | From 4.1.0 | 4.1.7 |
web-token/jwt-library Packagist | From 4.1.0 | 4.1.7 |
How do I fix GHSA-6vvh-pxr4-25r7?
Apply the vendor's patch.
Is GHSA-6vvh-pxr4-25r7 being exploited?
There is no known exploitation of GHSA-6vvh-pxr4-25r7 in the wild and no public exploit code.