CVE-2026-27932: CWE-770: Allocation of Resources Without Limits or Throttling in authlib joserfc
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.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-27932 resides in the authlib joserfc Python library, which implements JSON Object Signing and Encryption (JOSE) standards. Specifically, in versions 1.6.2 and earlier, the library fails to impose limits on the 'p2c' (PBES2 Count) parameter extracted from the protected header of JSON Web Encryption (JWE) tokens when using Password-Based Encryption (PBES2) algorithms. The 'p2c' parameter controls the iteration count for the PBKDF2 key derivation function, which is computationally expensive. An attacker can craft a malicious JWE token with an extremely high iteration count (e.g., 2^31 - 1), causing the server to perform excessive CPU-intensive operations during token decryption. Because the library does not validate or throttle this parameter, it leads to resource exhaustion and a Denial of Service (DoS) attack. This vulnerability affects all high-level JWE and JWT decryption interfaces that allow PBES2 algorithms, making it a broad risk for applications relying on joserfc for secure token handling. The attack requires no authentication or user interaction, increasing its risk profile. Although no known exploits are currently reported, the vulnerability's nature and ease of exploitation make it a significant threat. The CVSS v3.1 base score is 7.5, reflecting high severity due to network attack vector, no privileges required, no user interaction, and a high impact on availability.
Potential Impact
The primary impact of CVE-2026-27932 is a Denial of Service (DoS) condition caused by CPU exhaustion. Organizations using the vulnerable joserfc library for decrypting JWE tokens with PBES2 algorithms may experience service outages or degraded performance when processing maliciously crafted tokens. This can disrupt authentication, authorization, or other security-critical workflows relying on token validation, potentially affecting user access and system availability. The vulnerability does not directly compromise confidentiality or integrity but can indirectly impact business operations and user trust due to service unavailability. Since the attack requires no authentication and can be launched remotely, it poses a significant risk to internet-facing services and APIs using joserfc. The broad applicability to all high-level JWE/JWT decryption interfaces that permit PBES2 algorithms increases the attack surface. Organizations with high transaction volumes or critical authentication services using this library are particularly vulnerable to large-scale or targeted DoS attacks, which could lead to financial loss, reputational damage, and operational disruption.
Mitigation Recommendations
To mitigate CVE-2026-27932, organizations should immediately upgrade the authlib joserfc library to a version beyond 1.6.2 where this vulnerability is fixed. If an upgrade is not immediately feasible, implement strict validation and bounding of the 'p2c' parameter in the application layer before passing tokens to joserfc for decryption. Specifically, enforce a maximum iteration count threshold that balances security and performance, rejecting tokens with excessively high values. Disable or avoid using PBES2 algorithms for JWE token encryption if not strictly necessary, or restrict their use to trusted sources. Employ rate limiting and anomaly detection on endpoints that accept JWE tokens to identify and block suspicious token decryption attempts. Monitor CPU usage patterns for unusual spikes that may indicate exploitation attempts. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block tokens with abnormal 'p2c' values. Regularly audit and update cryptographic libraries and dependencies to incorporate security patches promptly.
Affected Countries
United States, Germany, United Kingdom, France, Japan, South Korea, Canada, Australia, Netherlands, Sweden
CVE-2026-27932: CWE-770: Allocation of Resources Without Limits or Throttling in authlib joserfc
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.
AI-Powered Analysis
Technical Analysis
The vulnerability identified as CVE-2026-27932 resides in the authlib joserfc Python library, which implements JSON Object Signing and Encryption (JOSE) standards. Specifically, in versions 1.6.2 and earlier, the library fails to impose limits on the 'p2c' (PBES2 Count) parameter extracted from the protected header of JSON Web Encryption (JWE) tokens when using Password-Based Encryption (PBES2) algorithms. The 'p2c' parameter controls the iteration count for the PBKDF2 key derivation function, which is computationally expensive. An attacker can craft a malicious JWE token with an extremely high iteration count (e.g., 2^31 - 1), causing the server to perform excessive CPU-intensive operations during token decryption. Because the library does not validate or throttle this parameter, it leads to resource exhaustion and a Denial of Service (DoS) attack. This vulnerability affects all high-level JWE and JWT decryption interfaces that allow PBES2 algorithms, making it a broad risk for applications relying on joserfc for secure token handling. The attack requires no authentication or user interaction, increasing its risk profile. Although no known exploits are currently reported, the vulnerability's nature and ease of exploitation make it a significant threat. The CVSS v3.1 base score is 7.5, reflecting high severity due to network attack vector, no privileges required, no user interaction, and a high impact on availability.
Potential Impact
The primary impact of CVE-2026-27932 is a Denial of Service (DoS) condition caused by CPU exhaustion. Organizations using the vulnerable joserfc library for decrypting JWE tokens with PBES2 algorithms may experience service outages or degraded performance when processing maliciously crafted tokens. This can disrupt authentication, authorization, or other security-critical workflows relying on token validation, potentially affecting user access and system availability. The vulnerability does not directly compromise confidentiality or integrity but can indirectly impact business operations and user trust due to service unavailability. Since the attack requires no authentication and can be launched remotely, it poses a significant risk to internet-facing services and APIs using joserfc. The broad applicability to all high-level JWE/JWT decryption interfaces that permit PBES2 algorithms increases the attack surface. Organizations with high transaction volumes or critical authentication services using this library are particularly vulnerable to large-scale or targeted DoS attacks, which could lead to financial loss, reputational damage, and operational disruption.
Mitigation Recommendations
To mitigate CVE-2026-27932, organizations should immediately upgrade the authlib joserfc library to a version beyond 1.6.2 where this vulnerability is fixed. If an upgrade is not immediately feasible, implement strict validation and bounding of the 'p2c' parameter in the application layer before passing tokens to joserfc for decryption. Specifically, enforce a maximum iteration count threshold that balances security and performance, rejecting tokens with excessively high values. Disable or avoid using PBES2 algorithms for JWE token encryption if not strictly necessary, or restrict their use to trusted sources. Employ rate limiting and anomaly detection on endpoints that accept JWE tokens to identify and block suspicious token decryption attempts. Monitor CPU usage patterns for unusual spikes that may indicate exploitation attempts. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block tokens with abnormal 'p2c' values. Regularly audit and update cryptographic libraries and dependencies to incorporate security patches promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-25T03:11:36.688Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69a768b5d1a09e29cb82cc7f
Added to database: 3/3/2026, 11:03:17 PM
Last enriched: 3/3/2026, 11:17:37 PM
Last updated: 3/4/2026, 7:18:02 AM
Views: 29
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2732: CWE-862 Missing Authorization in shortpixel Enable Media Replace
MediumCVE-2026-2363: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in cbutlerjr WP-Members Membership Plugin
MediumCVE-2026-2025: CWE-200 Information Exposure in Mail Mint
HighCVE-2026-27012: CWE-306: Missing Authentication for Critical Function in devcode-it openstamanager
CriticalCVE-2026-28289: CWE-434: Unrestricted Upload of File with Dangerous Type in freescout-help-desk freescout
CriticalActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.