Key confusion via stale named return
Published Oct 23, 2026 · Updated Oct 23, 2026
Key confusion in Eclipse KeyPont GOSE before 1.0.0-rc4 allows attackers to select an unintended key via a JWT with an unknown kid. JwksTrustStore.Get overwrites its named return value while parsing a refreshed JWKS, then returns the last parsed key without an error when no identifier matches. An allowlisted issuer and a nonempty fetched key set are required; signature verification still runs, so this flaw alone does not enable token forgery.
Summary
What happened
Key confusion in Eclipse KeyPont GOSE before 1.0.0-rc4 allows attackers to select an unintended key via a JWT with an unknown kid. JwksTrustStore.Get overwrites its named return value while parsing a refreshed JWKS, then returns the last parsed key without an error when no identifier matches. An allowlisted issuer and a nonempty fetched key set are required; signature verification still runs, so this flaw alone does not enable token forgery.
The record
- CVE
- CVE-2026-89313
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Eclipse Foundation
- Product
- Eclipse KeyPont GOSE
- Classifications
- CWE-706
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.0.0-rc4
- Affected versionversion=0.7.5 <=0.13.0-rc1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Unknown-kid key-lookup reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us