CVE-2026-22817
JWT alg confusion may allow forged tokens before 4.11.4.
Is CVE-2026-22817 being exploited?
Not confirmed. CVE-2026-22817 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-22817?
CVE-2026-22817 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-22817?
Yes. A fix has been recorded for CVE-2026-22817. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What should I do about CVE-2026-22817?
Upgrade to 4.11.4+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
JWT alg header can influence verification; forged tokens may be accepted, risking remote auth bypass.
Patch when possible
- affected< 4.11.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.