CVE-2026-89314: Quadratic-time key_ops duplicate check lets a sub-1 MB JWKS body pin a CPU core for ~15 s

Published Oct 23, 2026
·
Updated

jwkFields.CheckConsistency detected duplicate keyops entries with a pairwise nested loop, making validation cost grow with the square of the entry count. Because the check runs on every JWK and JWKS unmarshal, a modestly sized but hostile JWKS document could occupy a CPU core for many seconds.

Affected Software

1 affected component
lestrrat-go jwx

Event History

Oct 23, 2026
CVE Published
via MITRE·08:43 AM
Data Sourced
via MITRE·08:43 AM
DescriptionWeakness

Frequently Asked Questions

1

What inputs can trigger the excessive CPU use?

A hostile JWK or JWKS document containing a large number of key_ops entries can trigger it. The duplicate check is performed during every JWK and JWKS unmarshal.

2

Does an attacker need to send a large payload?

No. The issue can be triggered by a JWKS body smaller than 1 MB, while the quadratic duplicate check can occupy a CPU core for roughly 15 seconds.

3

Who is exposed in practice?

Applications that unmarshal JWK or JWKS data from attacker-controlled or otherwise untrusted sources are exposed to CPU exhaustion. Repeated processing of hostile documents could tie up available CPU capacity.

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