{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-33668", "tracking": { "current_release_date": "2026-03-27T20:38:17.878065Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-33668", "initial_release_date": "2026-03-24T20:51:37.626161Z", "revision_history": [ { "date": "2026-03-24T20:51:37.626161Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (6).| CWES updated (1)." }, { "date": "2026-03-24T20:51:40.130675Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-24T20:57:43.786953Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (1).| References created (6).| CWES updated (1)." }, { "date": "2026-03-24T20:57:46.064592Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-03-25T21:49:53.408024Z", "number": "5", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (8).| CWES updated (1)." }, { "date": "2026-03-25T21:50:00.595567Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-03-26T00:12:45.425804Z", "number": "7", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (1).| References created (7).| CWES updated (1)." }, { "date": "2026-03-26T00:12:55.773470Z", "number": "8", "summary": "NCSC Score updated." }, { "date": "2026-03-26T00:50:06.120095Z", "number": "9", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-26T20:39:11.016859Z", "number": "10", "summary": "Unknown change." }, { "date": "2026-03-26T20:40:00.977933Z", "number": "11", "summary": "NCSC Score updated." }, { "date": "2026-03-27T00:14:07.285352Z", "number": "12", "summary": "Source created.| CVE status created. (valid)| Description created for source.| References created (7)." }, { "date": "2026-03-27T19:47:08.200467Z", "number": "13", "summary": "CVSS created.| Products created (1).| Product Identifiers created (1).| Exploits created (1)." }, { "date": "2026-03-27T19:47:11.436451Z", "number": "14", "summary": "NCSC Score updated." } ], "status": "interim", "version": "14" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/>=0.18.0|<2.2.1", "product": { "name": "vers:unknown/>=0.18.0|<2.2.1", "product_id": "CSAFPID-5911159" } } ], "category": "product_name", "name": "api" }, { "branches": [ { "category": "product_version_range", "name": "vers:unknown/>=0.18.0|<2.2.1", "product": { "name": "vers:unknown/>=0.18.0|<2.2.1", "product_id": "CSAFPID-5902919" } } ], "category": "product_name", "name": "vikunja" } ], "category": "vendor", "name": "go-vikunja" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/>=0.18.0|<2.2.1", "product": { "name": "vers:unknown/>=0.18.0|<2.2.1", "product_id": "CSAFPID-5944024", "product_identification_helper": { "cpe": "cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*" } } } ], "category": "product_name", "name": "vikunja" } ], "category": "vendor", "name": "vikunja" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-33668", "cwe": { "id": "CWE-863", "name": "Incorrect Authorization" }, "notes": [ { "category": "description", "text": "Vikunja is an open-source self-hosted task management platform. Starting in version 0.18.0 and prior to version 2.2.1, 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. Version 2.2.1 patches the issue.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33668" }, { "category": "description", "text": "Vikunja is an open-source self-hosted task management platform. Starting in version 0.18.0 and prior to version 2.2.1, 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. Version 2.2.1 patches the issue.", "title": "cveprojectv5 - https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33668.json" }, { "category": "description", "text": "## Summary\n\nWhen 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.\n\n## Details\n\nUser status (`StatusDisabled`, `StatusAccountLocked`) is checked in only two places:\n\n1. **Local/LDAP login** (`pkg/routes/api/v1/login.go:74`) — prevents issuing new JWTs\n2. **JWT token refresh** (`pkg/routes/api/v1/login.go:247`) — prevents refreshing expired JWTs\n\nThree other authentication paths fetch the user from the database via `GetUserByID` but never inspect the returned user's status:\n\n### 1. API Token Authentication (`pkg/routes/api_tokens.go:76-103`)\n\nAPI 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.\n\n### 2. CalDAV Basic Auth (`pkg/routes/caldav/auth.go`)\n\nThe 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.\n\n### 3. OpenID Connect Callback (`pkg/modules/auth/openid/openid.go`)\n\nThe 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.\n\n## Impact\n\nAn administrator who disables a user account expects that user to be immediately locked out. In practice:\n\n- **API tokens**: The user retains full API access for the remaining lifetime of any issued API tokens — potentially months or years.\n- **CalDAV**: The user can continue reading and writing tasks/events via any CalDAV client.\n- **OIDC**: The user can obtain a fresh, fully valid JWT by re-authenticating through their identity provider, completely bypassing the account disable.\n\n## Proof of Concept\n\n1. Create a user and generate an API token.\n2. Disable the user account via the admin API or CLI.\n3. Make an API request using the API token:\n ```bash\n curl -H \"Authorization: Bearer tk_\" https://vikunja.example/api/v1/user\n ```\n4. The request succeeds with a 200 response despite the account being disabled.", "title": "github - https://api.github.com/advisories/GHSA-94xm-jj8x-3cr4" }, { "category": "description", "text": "## Summary\n\nWhen 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.\n\n## Details\n\nUser status (`StatusDisabled`, `StatusAccountLocked`) is checked in only two places:\n\n1. **Local/LDAP login** (`pkg/routes/api/v1/login.go:74`) — prevents issuing new JWTs\n2. **JWT token refresh** (`pkg/routes/api/v1/login.go:247`) — prevents refreshing expired JWTs\n\nThree other authentication paths fetch the user from the database via `GetUserByID` but never inspect the returned user's status:\n\n### 1. API Token Authentication (`pkg/routes/api_tokens.go:76-103`)\n\nAPI 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.\n\n### 2. CalDAV Basic Auth (`pkg/routes/caldav/auth.go`)\n\nThe 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.\n\n### 3. OpenID Connect Callback (`pkg/modules/auth/openid/openid.go`)\n\nThe 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.\n\n## Impact\n\nAn administrator who disables a user account expects that user to be immediately locked out. In practice:\n\n- **API tokens**: The user retains full API access for the remaining lifetime of any issued API tokens — potentially months or years.\n- **CalDAV**: The user can continue reading and writing tasks/events via any CalDAV client.\n- **OIDC**: The user can obtain a fresh, fully valid JWT by re-authenticating through their identity provider, completely bypassing the account disable.\n\n## Proof of Concept\n\n1. Create a user and generate an API token.\n2. Disable the user account via the admin API or CLI.\n3. Make an API request using the API token:\n ```bash\n curl -H \"Authorization: Bearer tk_\" https://vikunja.example/api/v1/user\n ```\n4. The request succeeds with a 200 response despite the account being disabled.", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-94xm-jj8x-3cr4.json?alt=media" }, { "category": "description", "text": "Vikunja Allows Disabled/Locked User Accounts to Authenticate via API Tokens, CalDAV, and OpenID Connect in code.vikunja.io/api.\n\nNOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.\n\n(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)\n\nThe additional affected modules and versions are: code.vikunja.io/api before v2.2.1.", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4849.json?alt=media" }, { "category": "other", "text": "0.00126", "title": "EPSS" }, { "category": "other", "text": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "title": "CVSSV4" }, { "category": "other", "text": "7.1", "title": "CVSSV4 base score" }, { "category": "other", "text": "3.5", "title": "NCSC Score" }, { "category": "other", "text": "Is related to CWE-863 (Incorrect Authorization)", "title": "NCSC Score top increasing factors" }, { "category": "other", "text": "Exploit code publicly available, There is exploit data available from source Nvd, Is related to (a version of) an uncommon product", "title": "NCSC Score top decreasing factors" } ], "product_status": { "known_affected": [ "CSAFPID-5902919", "CSAFPID-5911159", "CSAFPID-5944024" ] }, "references": [ { "category": "external", "summary": "Source - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33668" }, { "category": "external", "summary": "Source - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33668.json" }, { "category": "external", "summary": "Source - github", "url": "https://api.github.com/advisories/GHSA-94xm-jj8x-3cr4" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-94xm-jj8x-3cr4.json?alt=media" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4849.json?alt=media" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/go-vikunja/vikunja/commit/033922309f492996c928122fb49b691339199c35" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/go-vikunja/vikunja/commit/04704e0fde4b027039cf583110cee7afe136fc1b" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/go-vikunja/vikunja/commit/0b04768d830c80e9fde1b0962db1499cc652da0e" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/go-vikunja/vikunja/commit/fd452b9cb6457fd4f9936527a14c359818f1cca7" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-94xm-jj8x-3cr4" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://vikunja.io/changelog/vikunja-v2.2.2-was-released" }, { "category": "external", "summary": "Reference - github; osv", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33668" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/advisories/GHSA-94xm-jj8x-3cr4" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "baseScore": 8.1, "baseSeverity": "HIGH" }, "products": [ "CSAFPID-5902919", "CSAFPID-5911159", "CSAFPID-5944024" ] } ], "title": "CVE-2026-33668" } ] }