code.vikunja.io/api
Affected
- introduced
0.18.0, fixed2.2.1(semver)
Fixed versions
2.2.1
Fix
- Fixed version
2.2.1go get code.vikunja.io/[email protected]
Advisory
Also known as: CVE-2026-33668, GO-2026-4849
Vikunja Allows Disabled/Locked User Accounts to Authenticate via API Tokens, CalDAV, and OpenID Connect
Summary
When a user account is disabled or locked, the status check is only enforced on the local login and JWT token refresh paths. Three other authentication paths — API tokens, CalDAV basic auth, and OpenID Connect — do not verify user status, allowing disabled or locked users to continue accessing the API and syncing data.
Details
User status (StatusDisabled, StatusAccountLocked) is checked in only two places:
pkg/routes/api/v1/login.go:74) — prevents issuing new JWTspkg/routes/api/v1/login.go:247) — prevents refreshing expired JWTsThree other authentication paths fetch the user from the database via GetUserByID but never inspect the returned user's status:
1. API Token Authentication (pkg/routes/api_tokens.go:76-103)
API tokens are long-lived (up to years) and have no refresh cycle. A disabled user's API tokens remain fully functional until they expire naturally.
2. CalDAV Basic Auth (pkg/routes/caldav/auth.go)
The CalDAV basic auth handler validates credentials but does not check user status before granting access. A disabled user with valid credentials or a CalDAV token can continue syncing calendars and tasks.
3. OpenID Connect Callback (pkg/modules/auth/openid/openid.go)
The OIDC callback issues a fresh JWT token after validating the identity provider's response but does not check whether the Vikunja user account is disabled. If the user's identity provider session is still active, they receive a valid JWT despite being disabled in Vikunja.
Impact
An administrator who disables a user account expects that user to be immediately locked out. In practice:
Proof of Concept
curl -H "Authorization: Bearer tk_<token>" https://vikunja.example/api/v1/user
High Basis: The source's own band: HIGH
0.18.0, fixed 2.2.1 (semver)2.2.1
2.2.1go get code.vikunja.io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0