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


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-r56w-f43c-828p

## What is CVE-2026-89314?

CVE-2026-89314 is a medium-severity vulnerability in Eclipse KeyPont - GOSE, published on 23 Oct 2026. 

### Official description

`jwkFields.CheckConsistency` detected duplicate `key_ops` 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.

Weakness: CWE-407 (Inefficient Algorithmic Complexity)

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


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

No fix has been published for CVE-2026-89314 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-89314 being exploited?

There is no known exploitation of CVE-2026-89314 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89314 is a medium-severity vulnerability in Eclipse KeyPont - GOSE, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-89314 in the wild and no public exploit code.

Affected product: Eclipse KeyPont - GOSE. 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-89314/ (Markdown: https://insights.sbomify.com/CVE-2026-89314/index.md)
```

## Sources

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

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