Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Search

Search Results (4 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-134461 2 Nats, Web-token 3 Jwt Library, Jwt-framework, Jwt-library 2026-11-21 7.5 High
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.
CVE-2026-134459 2 Nats, Web-token 3 Jwt Library, Jwt-framework, Jwt-library 2026-11-21 5.9 Medium
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.
CVE-2026-134458 1 Nats 1 Jwt Library 2026-11-21 5.9 Medium
web-token jwt-framework and jwt-library before 3.4.12, 4.0.x before 4.0.8, 4.1.x before 4.1.10, and 4.2.x before 4.2.4, and jwt-encryption-algorithm-ecdh-es through 3.2.10, have a ConcatKDF::generate() that performs a single SHA-256 round, deriving at most 32 bytes for ECDH-ES and ECDH-SS direct key agreement. Anyone holding a JWE using A256CBC-HS512 can decrypt it under an all-zero AES key, while A192CBC-HS384 content keys have only 64-bit strength.
CVE-2021-3127 2 Linuxfoundation, Nats 2 Nats-server, Jwt Library 2026-03-30 7.5 High
NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled.