Eclipse KeyPont GOSE accepts JWS tokens with unenforced crit header
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-347.
Summary
Eclipse KeyPont - GOSE versions from 0.7.3 through 0.13.0-rc1 and versions before 1.0.0-rc4 are affected. The JWS verifier parses the crit header but never checks it, so it accepts tokens that list critical extensions it does not understand (CWE-347). A remote attacker without privileges can send such a token, but the attack is hard to carry out and its impact is limited to integrity.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
Description from the CNA
gose parsed the JWS `crit` header into `JwsHeader.Crit` and then never read it. RFC 7515 §4.1.11 requires a recipient to reject a JWS whose listed critical extension parameters it does not understand. gose implements no header extensions, so every token carrying a non-empty `crit` should have been rejected — and none were.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Eclipse Foundation | Eclipse KeyPont - GOSE | 0.7.3 – 0.13.0-rc1 | — | No fix listed | CNA |
| Eclipse Foundation | Eclipse KeyPont - GOSE | before 1.0.0-rc4 | 1.0.0-rc4 | Patch available | CNA |
- Eclipse KeyPont - GOSE VendorEclipse Foundation Affected 0.7.3 – 0.13.0-rc1 Fixed in — No fix listed CNA
- Eclipse KeyPont - GOSE VendorEclipse Foundation Affected before 1.0.0-rc4 Fixed in 1.0.0-rc4 Patch available CNA
Remediation
Upgrade Eclipse KeyPont - GOSE to 1.0.0-rc4, which fixes the flaw. The sources list no fixed version for Eclipse KeyPont - GOSE 0.7.3 through 0.13.0-rc1.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
- Fix · CNA Eclipse KeyPont - GOSE (Eclipse Foundation) Fixed in 1.0.0-rc4
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Eclipse KeyPont - GOSE 1.0.0-rc4
7 records Highest priority Priority HIGH 3 HIGH, 3 MEDIUM, 1 LOW
Other records, highest priority first
- TI-2026-79602 Panic on malformed JWE IV length in Eclipse KeyPont GOSEPriority HIGH 70
- TI-2026-79599 Panic in Eclipse KeyPont - GOSE JWT claim marshallingPriority HIGH 70
- TI-2026-79598 Slow duplicate key_ops check in Eclipse KeyPont GOSE exhausts CPUPriority HIGH 70
Timeline
- 2026-10-23 Threatist record created from CVE-2026-89317
- 2026-10-23 Priority changed: MEDIUM → LOW
- 2026-11-02 CISA SSVC decision points changed
- 2026-11-02 Priority changed: LOW → MEDIUM
More Eclipse Foundation vulnerabilities
- TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
- TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
- TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
- TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
- TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
- TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences