CVE-2026-33996 | benmcollins libjwt up to 3.2.x JWK Parser null pointer dereference (EUVD-2026-16899)

VDB-354063 · CVE-2026-33996 · EUVD-2026-16899 BENMCOLLINS LIBJWT UP TO 3.2.X JWK PARSER NULL POINTER DEREFERENCE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.4 $0-$5k 5.86- Summaryinfo A vulnerability has been found in benmcollins libjwt up to 3.2.x and classified as problematic. The affected element is an unknown function of the component JWK Parser. Performing a manipulation results in null pointer dereference. This vulnerability was named CVE-2026-33996. The attack needs to be approached within the local network. There is no available exploit. The affected component should be upgraded. Detailsinfo A vulnerability, which was classified as problematic, was found in benmcollins libjwt up to 3.2.x. This affects an unknown part of the component JWK Parser. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: LibJWT is a C JSON Web Token Library. Starting in version 3.0.0 and prior to version 3.3.0, the JWK parsing for RSA-PSS did not protect against a NULL value when expecting to parse JSON string values. A specially crafted JWK file could exploit this behavior by using integers in places where the code expected a string. This was fixed in v3.3.0. A workaround is available. Users importing keys through a JWK file should not do so from untrusted sources. Use the `jwk2key` tool to check for validity of a JWK file. Likewise, if possible, do not use JWK files with RSA-PSS keys. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-33996 since 03/24/2026. The exploitability is told to be difficult. The attack needs to be done within the local network. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. Upgrading to version 3.3.0 eliminates this vulnerability. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-16899). Productinfo Vendor benmcollins Name libjwt Version 3.0 3.1 3.2 Website Product: https://github.com/benmcollins/libjwt/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 4.6 VulDB Meta Temp Score: 4.4 VulDB Base Score: 4.6 VulDB Temp Score: 4.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Null pointer dereference CWE: CWE-476 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: libjwt 3.3.0 Timelineinfo 03/24/2026 CVE reserved 03/27/2026 +3 days Advisory disclosed 03/27/2026 +0 days VulDB entry created 03/28/2026 +1 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-33996 (🔒) GCVE (CVE): GCVE-0-2026-33996 GCVE (VulDB): GCVE-100-354063 EUVD: 🔒 Entryinfo Created: 03/27/2026 23:54 Updated: 03/28/2026 04:36 Changes: 03/27/2026 23:54 (67), 03/28/2026 04:36 (1) Complete: 🔍 Cache ID: 99:18E:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸