Loading vulnerability…
CVE-2026-71206 is an authentication and authorization flaw in Shiori caused by improper handling of JWT-backed sessions in the CheckToken function within internal/domains/auth.go. The function validates only the JWT HMAC signature and then trusts the embedded account claims object as authoritative, returning it without re-fetching the current account record from persistent storage. Because the application does not implement a session store or token revocation mechanism, previously issued tokens remain valid even after the corresponding account is deleted or its role is downgraded. As a result, a token issued to an owner account can continue to authenticate successfully with the original owner-level privileges until the token naturally expires, including for extended periods when long-lived login options are enabled.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.