# CVE-2026-92091: Jwcrypto: jwcrypto: denial of service via o(n^2) duplicate check on unbounded jwk key_ops array

> Remote attackers can cause denial of service by sending large JWK key_ops arrays to applications using the JWCrypto library for key import.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** AZL-103095, DEBIAN-CVE-2026-92091, OESA-2026-4066, SUSE-SU-2026:24218-1, UBUNTU-CVE-2026-92091, openSUSE-SU-2026:11972-1, openSUSE-SU-2026:22073-1

## What is CVE-2026-92091?

CVE-2026-92091 is a medium-severity denial of service vulnerability in Red Hat Ansible Automation Platform 2, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in jwcrypto. The JWK.import_key() function validates the key_ops JWK member for duplicate values using an algorithm with O(n^2) time complexity, and the length of key_ops is not bounded. A remote, unauthenticated attacker can supply a JWK with a large key_ops array to an application that passes attacker-controlled key material to a public key-import API (reachable via ECDH-ES key agreement, OIDC dynamic client registration, DPoP, or ACME account key registration, among others) to consume excessive CPU time, resulting in a denial of service.

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

## Which versions are affected by CVE-2026-92091?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-jwcrypto` | SUSE:Linux Enterprise Server 16.0 | All versions | 1.5.6-160000.5.1 |
| `python-jwcrypto` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.5.6-160000.5.1 |
| `python-jwcrypto` | openSUSE:Leap 16.0 | All versions | 1.5.6-160000.5.1 |
| `python-jwcrypto` | openSUSE:Tumbleweed | All versions | 1.6.1-1.1 |

## How do I fix CVE-2026-92091?

Upgrade to a fixed version.

## Is CVE-2026-92091 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92091 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92091 and fix it if it is affected.

What it is: CVE-2026-92091 is a medium-severity denial of service vulnerability in Red Hat Ansible Automation Platform 2, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92091 exists.

Affected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92091/ (Markdown: https://insights.sbomify.com/CVE-2026-92091/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92091
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92091
- OSV: https://osv.dev/vulnerability/CVE-2026-92091

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92091/
Summaries are generated and may contain mistakes; the official description above is the record.
