CVE-2025-65015 Details
Description
joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. In versions from 1.3.3 to before 1.3.5 and from 1.4.0 to before 1.4.2, the ExceededSizeError exception messages are embedded with non-decoded JWT token parts and may cause Python logging to record an arbitrarily large, forged JWT payload. In situations where a misconfigured — or entirely absent — production-grade web server sits in front of a Python web application, an attacker may be able to send arbitrarily large bearer tokens in the HTTP request headers. When this occurs, Python logging or diagnostic tools (e.g., Sentry) may end up processing extremely large log messages containing the full JWT header during the joserfc.jwt.decode() operation. The same behavior also appears when validating claims and signature payload sizes, as the library raises joserfc.errors.ExceededSizeError() with the full payload embedded in the exception message. Since the payload is already fully loaded into memory at this stage, the library cannot prevent or reject it. This issue has been patched in versions 1.3.5 and 1.4.2.
A vulnerability exists in the joserfc library, which implements JSON Object Signing and Encryption (JOSE) standards. In versions 1.3.3 prior to 1.3.5 and 1.4.0 prior to 1.4.2, the ExceededSizeError exception messages include non-decoded parts of JWT tokens, potentially causing Python logging to record large, forged JWT payloads. This issue can be exploited when a misconfigured or absent production-grade web server allows the sending of large bearer tokens in HTTP request headers. The vulnerability leads to excessive resource consumption, as the full JWT header is processed and logged, including in diagnostic tools like Sentry. The problem arises because the payload is loaded into memory before the library can reject it, creating a risk of uncontrolled resource consumption.
Users can update to joserfc versions 1.3.5 or 1.4.2, both of which address the vulnerability by removing the raw JWT payload from the ExceededSizeError exception messages. Additionally, it is recommended to configure the web server or reverse proxy to enforce strict limits on header sizes.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 19, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| hsiaoming joserfc | >= 1.3.3, < 1.3.5 >= 1.4.0, < 1.4.2 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 18, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jan 15, 2026 | Initial Analysis | [email protected] |
| Nov 19, 2025 | CVE Modified | CISA-ADP |
| Nov 18, 2025 | New CVE Received | [email protected] |