CVE-2026-55735
Unauthenticated JWT forgery allows forced logout by revoking victim sessions.
Is CVE-2026-55735 being exploited?
Not confirmed. CVE-2026-55735 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.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-55735?
CVE-2026-55735 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-55735?
Yes. A fix has been recorded for CVE-2026-55735. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55735 affect?
CVE-2026-55735 affects guardian (Elixir) >=1.0.0 <2.4.1, Elixir apps using Guardian revoke endpoints, Backends using claim-keyed revocation (e.g., GuardianDB). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55735?
Upgrade guardian to >=2.4.1 and ensure revoke checks token signatures before state changes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can forge JWTs to revoke victims' sessions (denial of service of user sessions) by exploiting Guardian.revoke/3 without signature verification.
Immediate action required
- affected>= 1.0.0 and < 2.4.1
- affected>= d65227145f72b290106c06cecbe42728fbf05fe2 and < 2bd7a8c29770d423d855c0a4965caa6c3e486901
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.