Loading vulnerability…
CVE-2026-68581 is an authentication bypass vulnerability in Vikunja affecting versions 0.22.0 through 2.3.0. The flaw stems from API token management logic that fails to validate the principal type when resolving identities. User IDs and link-share IDs are maintained as independent numeric sequences, but both are resolved through a generic identity interface. As a result, a link-share JWT whose numeric identifier collides with a legitimate user ID can be accepted by the /api/v1/tokens endpoints as if it represented that user. An authenticated attacker can first determine a target user’s numeric ID through authenticated user search, then create link shares on a project they can modify until a link-share ID matches the target user ID. The attacker can then present the corresponding link-share JWT to interact with the target user’s API token management functions.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
10 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.