How severe is CVE-2026-33668?

No CVSS score has been assigned to CVE-2026-33668 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-33668?

CVE-2026-33668 affects the following packages: code.vikunja.io/api (Go). Ecosystems affected: Go.

How do I fix CVE-2026-33668?

Update code.vikunja.io/api to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33668 is resolved across your whole dependency graph.

How do I detect CVE-2026-33668 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.vikunja.io/api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-33668 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-33668 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-33668 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-33668?

CVE-2026-33668 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-33668?

CVE-2026-33668 is classified as CWE-285 (CWE-285), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-33668 published, and has it been updated?

CVE-2026-33668 was published on March 24, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-33668 — api

Fix: go-vikunja/vikunja@0339223

CVE-2026-33668 is a CWE-285 vulnerability in code.vikunja.io/api. A fix is available for code.vikunja.io/api — see the affected versions and patch details below.

Vikunja Allows Disabled/Locked User Accounts to Authenticate via API Tokens, CalDAV, and OpenID Connect

Also known asGHSA-94xm-jj8x-3cr4GO-2026-4849

Published

Mar 24, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33668.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹code.vikunja.io/api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

Local/LDAP login (pkg/routes/api/v1/login.go:74) — prevents issuing new JWTs
JWT token refresh (pkg/routes/api/v1/login.go:247) — prevents refreshing expired JWTs

Three 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:

API tokens: The user retains full API access for the remaining lifetime of any issued API tokens — potentially months or years.
CalDAV: The user can continue reading and writing tasks/events via any CalDAV client.
OIDC: The user can obtain a fresh, fully valid JWT by re-authenticating through their identity provider, completely bypassing the account disable.

Proof of Concept

Create a user and generate an API token.
Disable the user account via the admin API or CLI.

Make an API request using the API token:

curl -H "Authorization: Bearer tk_<token>" https://vikunja.example/api/v1/user

The request succeeds with a 200 response despite the account being disabled.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`code.vikunja.io/api`	≥ 0.18.0&&< 2.2.1	2.2.1`go get code.vikunja.io/api@v2.2.1`

Affected Products

1 product · 1 configurations

Application

vikunjavikunja

≥ 0.18.0 && < 2.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.vikunja.io/api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update code.vikunja.io/api to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33668 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## 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: 1. **Local/LDAP login** (`pkg/routes/api/v1/login.go:74`) — prevents issuing new JWTs 2. **JWT token refresh** (`pkg/routes/api/v1/login.go:247`) — prevents refreshing

O3 Security · Impact-Aware SCA

Is CVE-2026-33668 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works