Live › vulnerability › CVE-2026-119283
joserfc is a Python library for JOSE standards such as JWE and JWS. Before version 1.7.5, decrypt_json() runs a private-key decryption for every entry in a JWE recipients array with no limit, so one request can force many expensive RSA operations.
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.
Services that accept JWE General JSON Serialization input from untrusted clients and decrypt it with an RSA key-management algorithm using joserfc before 1.7.5. Applications that only verify JWS, use other key-management algorithms, or never decrypt attacker-supplied JWE can skip it. The sources describe a CPU exhaustion effect only, with no confidentiality or integrity impact.
No product ranges from the sources yet.
pip show joserfcjoserfc.jwe.decrypt_json on untrusted input that use RSA key-management algorithmsjoserfc 1.7.5Each 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.5, joserfc.jwe.decrypt_json() accepts a JWE General JSON Serialization recipients array without a count limit and calls decrypt_cek() for every entry. An unauthenticated attacker who can submit a JWE to an endpoint using an RSA key-management algorithm can choose the number of private-key decryption operations performed by one request. The verify_all_recipients option does not reduce this work because the affected loop processes every recipient before consulting that setting, allowing repeated requests to exhaust service CPU without affecting confidentiality or integrity. This issue is fixed in version 1.7.5.
This page as .md · .json · in your agent: get_signal("CVE-2026-119283")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.