# CVE-2026-89313: JwksTrustStore.Get returns the last fetched JWKS key (err=nil) when the requested kid is absent, instead of nil


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/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-v7r8-g6h9-99vv

## What is CVE-2026-89313?

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

### Official description

`JwksTrustStore.Get` assigned each parsed key to the function's **named return value** while refreshing the JWKS cache. When the requested `kid` was not present, the trailing naked `return` handed the caller the last key in the JWKS document together with a `nil` error — a confidently wrong answer instead of "not found".

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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


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

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

## Is CVE-2026-89313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89313 is a medium-severity vulnerability in Eclipse KeyPont - GOSE, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-89313 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-89313/ (Markdown: https://insights.sbomify.com/CVE-2026-89313/index.md)
```

## Sources

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

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