Search vulnerabilities

Results 3

CVE-2026-134461

Web-Token jwt-framework before 3.4.10 DoS via Unbounded PBES2 p2c Iteration Count

Web-Token jwt-framework and jwt-library before 3.4.10, 4.0.0 before 4.0.7, and 4.1.0 before 4.1.7 contain an uncontrolled resource consumption vulnerability in PBES2AESKW::unwrapKey(), which passes the attacker-controlled p2c JWE header value to hash_pbkdf2() without an upper bound. Unauthenticated attackers can send a JWE using a PBES2-HS*+A*KW algorithm with a huge p2c iteration count to force lengthy PBKDF2 computations and exhaust server CPU.

CVSS 4.0 · 8.7 High EPSS n/a KEV · Not listed
Vendors
CVE-2026-134460

web-token jwt-framework 1.2.0 before 3.4.10 Missing Authentication in Chacha20Poly1305 Key Encryption

web-token jwt-framework 1.2.0 before 3.4.10, jwt-experimental before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7 contain a missing integrity check in the experimental Chacha20Poly1305 key-encryption algorithm, which discards the Poly1305 tag in encryptKey() and calls openssl_decrypt() without it in decryptKey(). Attackers on the token path can modify the encrypted content encryption key undetected.

CVSS 4.0 · 6.3 Medium EPSS n/a KEV · Not listed
Vendors
CVE-2026-134459

web-token jwt-framework before 3.4.10 RSA1_5 Bleichenbacher Padding Oracle

web-token jwt-framework and jwt-library before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7 contain a padding oracle in RSACrypt::decryptWithRSA15() because RSA1_5 decryption lacks implicit rejection, so invalid padding, wrong CEK length, and valid padding take measurably different time. Remote attackers can submit adaptively crafted JWE encrypted_key values and measure these timing differences to recover the wrapped content encryption key.

CVSS 4.0 · 8.2 High EPSS n/a KEV · Not listed
Vendors