JWT expiration bypass in Perry verify_decode
CVE-2026-53776 affects Perry versions before 0.5.1166. The vulnerability is in the standard library JWT verification path, specifically the verify_decode helper, where validate_exp is unconditionally set to false. As a result, jwt.verify() accepts expired JSON Web Tokens instead of enforcing the exp claim. An attacker who has a previously issued bearer token can continue to authenticate with that token after its intended expiration, including after logout or administrative revocation events that rely on token expiry enforcement.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.