CVE-2026-89317: JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11)
Eclipse Foundation · Eclipse KeyPont - GOSE
Vendor fix available · Affected: Eclipse Foundation Eclipse KeyPont - GOSE · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 12% of scored CVEs
DescriptionCVE.org
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.
Affected products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Eclipse Foundation · Eclipse KeyPont - GOSEfrom 0.7.3 up to and including 0.13.0-rc1
- Eclipse Foundation · Eclipse KeyPont - GOSEbefore 1.0.0-rc4
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Eclipse Foundation
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-89317 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.