Summary
Vikunja has a 2FA Bypass via Caldav Basic Auth
Impact
Any user that has 2FA enabled could have it bypassed, allowing attacker access to a lot of the user's project information.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
If there are 2FA barriers to access an account in a specific fashion, all integrations should follow those if they're using the same methods of authentication. The easiest path is probably to disable Basic Authentication for Caldav by default, but keep the token access enabled, that way users can generate tokens specifically for Caldav if they want to use that feature. Basic Auth for it could be kept, but would most likely want to be a feature flag or something along those lines. That's so users can turn it on if it's necessary, but can be notified in the documentation that it's a more unsafe pattern if 2FA is enabled.
Frequently Asked Questions
- What is CVE-2026-33315? CVE-2026-33315 is a medium-severity security vulnerability in code.vikunja.io/api (go), affecting versions <= 2.1.0. No fixed version is listed yet.
- Which versions of code.vikunja.io/api are affected by CVE-2026-33315? code.vikunja.io/api (go) versions <= 2.1.0 is affected.
- Is there a fix for CVE-2026-33315? No fixed version is listed for CVE-2026-33315 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2026-33315 exploitable, and should I be worried? Whether CVE-2026-33315 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-33315 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.