CVE-2026-89317: gose parsed the JWS `crit` header into `JwsHeader.Crit` and then never read it
CVE-2026-89317 is a medium-severity flaw (CVSS 6.3) affecting affected software. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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 this priority
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-10-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-89317?
No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.
Is CVE-2026-89317 being exploited?
CVE-2026-89317 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-89317 affect?
CVE-2026-89317 affects affected software. Severity is medium (CVSS 6.3). 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, s
How urgent is CVE-2026-89317?
Priority 28/100. Remotely exploitable, no login, no user action