Loading vulnerability…
CVE-2026-68581 is an authentication bypass vulnerability in Vikunja affecting versions 0.22.0 through 2.3.0. The flaw exists in API token management because the application does not validate the principal type when resolving identities for the /api/v1/tokens endpoints. User identities and link-share identities are maintained as independent numeric sequences, but both are resolved through a generic identity lookup interface. As a result, a link-share JWT whose numeric identifier collides with a legitimate user identifier can be interpreted as that user when accessing token-management functionality. 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's ID. The attacker can then use the resulting link-share JWT to interact with the target user's API tokens as though they were the victim user.
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.
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.
11 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.