CVE-2026-89317: CWE-20 Improper Input Validation in Eclipse Foundation Eclipse KeyPont - GOSE
Description
CVE-2026-89317 is a medium severity vulnerability in Eclipse Foundation's Eclipse KeyPont - GOSE component. The vulnerability arises because the library parses the JWS 'crit' header but does not enforce the requirement to reject tokens with unrecognized critical extensions, as mandated by RFC 7515 §4.1.11. Since GOSE implements no header extensions, any token with a non-empty 'crit' header should have been rejected but was not.
CVSS v4.0
Score 6.3medium
Affected software
Eclipse Foundation
Eclipse KeyPont - GOSE
Eclipse Foundation
Eclipse KeyPont - GOSE
pkg:github/github.com/ThalesGroup/gosepkg:github/github.com/eclipse-keypont/goseRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Eclipse KeyPont - GOSE involves improper input validation of the JSON Web Signature (JWS) 'crit' header. According to RFC 7515 §4.1.11, recipients must reject JWS tokens containing critical extension parameters they do not understand. GOSE parses the 'crit' header into JwsHeader.Crit but never reads or enforces this field. Because GOSE does not implement any header extensions, it should reject any token with a non-empty 'crit' header, but it fails to do so, potentially allowing tokens with unrecognized critical extensions to be accepted.
Potential Impact
This vulnerability could allow acceptance of JWS tokens containing critical extension parameters that GOSE does not understand, violating the security expectations of RFC 7515. This may lead to improper token validation and potential security bypasses in systems relying on GOSE for JWS processing. The CVSS 4.0 base score is 6.3 (medium severity), reflecting network attack vector, high attack complexity, no privileges required, no user interaction, and limited impact on integrity.
Mitigation Recommendations
No official patch or fix is currently documented. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider additional validation of JWS tokens outside of GOSE to ensure tokens with non-empty 'crit' headers are rejected as required by RFC 7515.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- eclipse
- Date Reserved
- 2026-09-11T13:55:53.128Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6adb225b4d27ba8daaeddba4
Added to database: 10/23/2026, 09:01:15 UTC
Last enriched: 10/23/2026, 09:15:21 UTC
Last updated: 10/23/2026, 09:15:56 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.