Quick answers
- Is CVE-2026-92091 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92091 being exploited in the wild.
- How severe is CVE-2026-92091?
- Medium severity, with a CVSS score of 5.9, published 16 September 2026.
- Which products and versions are affected?
- jwcrypto jwcrypto <UNKNOWN>.
- Is there a fix for CVE-2026-92091?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92091 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92091?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in jwcrypto's JWK.import_key() function, which validates the key_ops JWK member for duplicate values using an O(n²) time complexity algorithm (nested loop comparison). The key_ops array length is not bounded during import, allowing an attacker to supply an arbitrarily large array. A remote, unauthenticated attacker can craft a JWK with a massive key_ops array and pass it to any public API that imports untrusted key material, such as ECDH-ES key agreement, OIDC dynamic client registration, DPoP token validation, or ACME account key registration. The inefficient duplicate-checking algorithm will consume excessive CPU cycles proportional to the square of the array length, resulting in denial of service. No patch or workaround is documented as of the advisory date.
Affected products
- jwcrypto jwcrypto <UNKNOWN>
Timeline
- 2026-09-16: disclosed: CVE-2026-92091 published