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.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 23 Oct 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11) | |
| Weaknesses | CWE-1288 CWE-20 CWE-347 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: eclipse
Published:
Updated: 2026-10-23T08:50:22.987Z
Reserved: 2026-09-11T13:55:53.128Z
Link: CVE-2026-89317
No data.
Status : Received
Published: 2026-10-23T09:17:08.260
Modified: 2026-10-23T09:17:08.260
Link: CVE-2026-89317
No data.
OpenCVE Enrichment
Updated: 2026-10-23T10:30:09Z