How severe is GHSA-94xm-jj8x-3cr4?

No CVSS score has been assigned to GHSA-94xm-jj8x-3cr4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-94xm-jj8x-3cr4?

GHSA-94xm-jj8x-3cr4 affects the following packages: code.vikunja.io/api (Go). Ecosystems affected: Go.

How do I fix GHSA-94xm-jj8x-3cr4?

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 GHSA-94xm-jj8x-3cr4 is resolved across your whole dependency graph.

How do I detect GHSA-94xm-jj8x-3cr4 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.vikunja.io/api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-94xm-jj8x-3cr4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-94xm-jj8x-3cr4?

O3 pinpoints whether GHSA-94xm-jj8x-3cr4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-94xm-jj8x-3cr4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-94xm-jj8x-3cr4 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 GHSA-94xm-jj8x-3cr4?

GHSA-94xm-jj8x-3cr4 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 36th 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.

When was GHSA-94xm-jj8x-3cr4 published, and has it been updated?

GHSA-94xm-jj8x-3cr4 was published on March 25, 2026 and was last updated on March 26, 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

GHSA-94xm-jj8x-3cr4

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

Also known asCVE-2026-33668GO-2026-4849

Published

Mar 25, 2026

Updated

Mar 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk36th percentile+0.35%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-94xm-jj8x-3cr4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-94xm-jj8x-3cr4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-94xm-jj8x-3cr4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-94xm-jj8x-3cr4 in your dependencies?

O3 detects GHSA-94xm-jj8x-3cr4 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works