Skip to main content
VulnerabilityPublished Updated

CVE-2026-55735: ueberauth guardian · Improper Verification of Cryptographic Signature

Affects ueberauth guardianSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2.4.1 soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.1, 2bd7a8c29770d423d855c0a4965caa6c3e486901
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade guardian to 2.4.1; guardian to 2bd7a8c29770d423d855c0a4965caa6c3e486901.

Affected software

ProductAffectedFixed in
ueberauthguardianAffected
  • >=1.0.0 <2.4.1
Fixed in
  • 2.4.1
ueberauthguardianAffected
  • ≥ d65227145f72b290106c06cecbe42728fbf05fe2, < 2bd7a8c29770d423d855c0a4965caa6c3e486901
Fixed in
  • 2bd7a8c29770d423d855c0a4965caa6c3e486901
Hexguardianpkg:hex/guardianOther threatsAffected
  • >=1.0.0 <2.4.1
Fixed in
  • 2.4.1

CPE configurations (1)

  • cpe:2.3:a:ueberauth:guardian:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid using the revoke/3 function with caller-supplied tokens or implement additional signature verification before calling revoke/3 to prevent unauthenticated session revocation.

Description

Improper Verification of Cryptographic Signature in ueberauth guardian allows an unauthenticated attacker to revoke a victim's session with a forged token. Guardian.revoke/3 in lib/guardian.ex decodes the supplied token with peek/1, which performs no signature verification (it only base64-decodes the JWT header and payload). The resulting unverified claims are forwarded directly to the configured token module's revoke callback and the implementation's on_revoke callback, a state-mutating sink. The sibling operations refresh/2 and exchange/4 both call decode_and_verify first, so the signature is checked before anything acts on the claims; revoke/3 is the only state-mutating path that acts on claims without verifying the signature. An attacker who knows or guesses a victim's identifying claim values (jti, sub) can forge a JWT carrying those claims, sign it with an arbitrary key, and submit it to any endpoint that funnels a caller-supplied token into Guardian.revoke/3 (the standard logout / session-revocation pattern). When the token module mutates state keyed by the claims (whitelist deletion or blacklist insertion, for example a GuardianDb-style store), the victim's legitimate session is evicted. This is an unauthenticated session-revocation denial of service; the attacker never needs the signing secret. This issue affects guardian: from 1.0.0 before 2.4.1.

References

Community reviews

Loading reviews…