CVE-2026-80179: Jwcrypto: jwcrypto: denial of service via malformed jwe tokens

Published Aug 25, 2026
·
Updated

A flaw was found in jwcrypto. A remote attacker can send a specially crafted JSON Web Encryption (JWE) token containing numerous period delimiters. This malformed token can force the JWE.deserialize() function to allocate excessive memory, leading to a MemoryError. This issue results in a denial of service (DoS) for services that process untrusted JWE values.

Other sources

The compact JWE fallback in JWE.deserialize() splits attacker-controlled token text on every period delimiter before checking that the compact serialization has the required five segments. A malformed token containing millions of periods can therefore force a large delimiter-derived list allocation and raise MemoryError before jwcrypto reaches its normal malformed-token rejection, which can degrade availability for services that parse untrusted JWE values.

Red Hat

Affected Software

1 affected component
jwcrypto

Event History

Aug 25, 2026
Data Sourced
via Red Hat·09:56 PM
DescriptionSeverityAffected Software
Aug 27, 2026
CVE Published
via MITRE·09:14 PM
Data Sourced
via MITRE·09:14 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service condition?

Services using jwcrypto that pass untrusted JWE token values to JWE.deserialize() are exposed. The issue can degrade availability when an attacker can submit malformed token text to a code path that parses it.

2

What does an attacker need to exploit the issue?

An attacker needs network access to a service that processes attacker-controlled JWE values. No authentication or user interaction is required, but the attacker must send a malformed token containing a very large number of period delimiters.

3

What is the operational impact of a successful attack?

The crafted token can cause excessive memory allocation during delimiter splitting and raise MemoryError before normal malformed-token validation occurs. This can deny service or degrade availability of the affected parsing service.

4

How can teams determine whether they are affected?

Identify whether the application uses jwcrypto's JWE.deserialize() on JWE values received from untrusted sources. Review inbound token-processing paths, such as externally supplied requests or messages, for values passed into that function.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203