Medium severity · published Mar 27, 2026
CVE-2026-33996
LibJWT has NULL/bounds validation in JWK octet and RSA PSS parsing
5.5
CVSS
0.2%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 5% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
LI
libjwt · benmcollins
>= 3.0.0, < 3.3.0 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-33996
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-33996
Patch
https://github.com/benmcollins/libjwt/commit/cfd890286fa49ae61b534c937c9f0428b5c6034c
Mitigation
https://github.com/benmcollins/libjwt/security/advisories/GHSA-ph96-hqpc-9f66
More from libjwt
9.1
CVE-2026-44699
LibJWT: Algorithm confusion allows JWT forgery with RSA JWK as empty-key HMAC
