CVE-2026-27932 Details
Description
joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. In 1.6.2 and earlier, a resource exhaustion vulnerability in joserfc allows an unauthenticated attacker to cause a Denial of Service (DoS) via CPU exhaustion. When the library decrypts a JSON Web Encryption (JWE) token using Password-Based Encryption (PBES2) algorithms, it reads the p2c (PBES2 Count) parameter directly from the token's protected header. This parameter defines the number of iterations for the PBKDF2 key derivation function. Because joserfc does not validate or bound this value, an attacker can specify an extremely large iteration count (e.g., 2^31 - 1), forcing the server to expend massive CPU resources processing a single token. This vulnerability exists at the JWA layer and impacts all high-level JWE and JWT decryption interfaces if PBES2 algorithms are allowed by the application's policy.
A denial-of-service vulnerability has been identified in the joserfc library, which implements JSON Object Signing and Encryption (JOSE) standards. This vulnerability exists in versions through 1.6.2 and allows an unauthenticated attacker to cause CPU exhaustion. The issue arises when the library decrypts a JSON Web Encryption (JWE) token using Password-Based Encryption (PBES2) algorithms. joserfc reads the p2c (PBES2 Count) parameter directly from the token's protected header, which specifies the number of iterations for the PBKDF2 key derivation function. However, joserfc does not validate or limit this value, enabling an attacker to specify a very high iteration count, such as 2^31 - 1. This forces the server to use significant CPU resources to process the token. The vulnerability affects all high-level JWE and JWT decryption interfaces that allow PBES2 algorithms, as the exhaustion occurs during decryption, before any claim validation or signature verification.
Users are advised to update to joserfc version 1.6.3, where this vulnerability has been addressed by implementing a maximum limit for the p2c parameter. Additionally, applications should only enable PBES2 algorithms if necessary and enforce a strict allowlist of algorithms in their JWT/JWE policies.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Mar 4, 2026References 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.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/authlib/joserfc/commit/696a9611ab982c45ee2190ed79ca8e1d8e09398f | [email protected] | Patch |
| https://github.com/authlib/joserfc/security/advisories/GHSA-w5r5-m38g-f9f9 | [email protected] | ExploitMitigationVendor Advisory |
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.6.2 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Mar 5, 2026 | Initial Analysis | [email protected] |
| Mar 3, 2026 | New CVE Received | [email protected] |