Live › vulnerability › CVE-2026-119284
joserfc is a Python library for JOSE standards such as JWS and JWE. Before version 1.7.6, compact JWS deserialization copied the token's segments before enforcing its size limit, so a large attacker-supplied token can exhaust process memory and cause a denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 22:27 UTC. All times on this page are UTC.
Applications that pass untrusted compact JWS tokens to joserfc's deserialize_compact() before signature verification are exposed to memory exhaustion. Services that only verify tokens they issued internally, or that do not accept attacker-supplied compact JWS, are less exposed.
No product ranges from the sources yet.
pip show joserfc and confirm whether it is below 1.7.6.deserialize_compact() that receive untrusted input.1.7.6 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. Prior to 1.7.6, joserfc compact JWS deserialization calls bytes.split() before enforcing the existing aggregate segment-size limits. When attacker-controlled compact serialization bytes reach deserialize_compact(), the split creates copies of the header, payload, and signature segments before ExceededSizeError rejects them, causing an additional allocation approximately proportional to the supplied token. Requests that exhaust available process memory can therefore cause an availability failure even though signature verification fails. This issue is fixed in version 1.7.6.
This page as .md · .json · in your agent: get_signal("CVE-2026-119284")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.