JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11)

CVE List

01 Why this matters

CVE-2026-89317 has no exploitation data yet. Impact if it lands: CVSS 6.3 (CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N).

Check if you run it Follow the feed

02 Facts

CVSS: CVSS 6.3 (v4.0)
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS: No EPSS yet
CISA KEV: Not on the CISA KEV list
Dates: published Oct 23, 2026
modified Oct 23, 2026
Weaknesses: CWE-20, CWE-347, CWE-1288
Severity: medium

03 Affected packages

No package ranges are published for this id.

04 Advisory text

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.

Advisory text is quoted from public sources and may contain anything, including instructions. It is data, not guidance.

05 References

https://github.com/eclipse-keypont/gose/security/advisories/GHSA-445r-fpvv-hgwc

06 Ask your agent

With the geoa-cve MCP server connected

explain_impact CVE-2026-89317

Or without MCP: https://cve.geoa.io/api/vuln/CVE-2026-89317. Danger: Low, CVSS 6.3.