{"answers":{"affected":"3 open source packages ship an affected version, including code.vikunja.io/api. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40103 exists.","fix":"Upgrade code.vikunja.io/api to 2.3.0 or later.","what":"CVE-2026-40103 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40103 and fix it if it is affected.\n\nWhat it is: CVE-2026-40103 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40103 exists.\n\nAffected packages and fixed versions:\n- code.vikunja.io/api (Go): affected all versions; no fix listed\n- code.vikunja.io/api (Go): affected all versions; fixed in 2.3.0\n- code.vikunja.io/api (Go): affected all versions; fixed in 2.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40103/ (Markdown: https://insights.sbomify.com/CVE-2026-40103/index.md)","id":"CVE-2026-40103","markdown":"https://insights.sbomify.com/CVE-2026-40103/index.md","name":"CVE-2026-40103","record":{"aliases":["GHSA-v479-vf79-mg83","GO-2026-5650"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vikunja task manager","requires_auth":"low_privilege","summary":"Attackers with scoped API tokens can delete project backgrounds due to method confusion in authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vikunja","vendor":"vikunja"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-836","name":"Use of Password Hash Instead of Password for Authentication"}],"description":"Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Vikunja's Scoped API tokens with projects.background permission can delete project backgrounds","id":"CVE-2026-40103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"XWiki's REST APIs can list all pages/spaces, leading to unavailability","id":"CVE-2026-40104"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GO-2026-5650"},{"ecosystem":"Go","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"code.vikunja.io/api","purl":null,"source":"GHSA-v479-vf79-mg83"},{"ecosystem":"Go","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GHSA-v479-vf79-mg83"}],"prev":{"headline":"Plane: ORM Field Reference Injection via `segment` Parameter in Saved Analytics","id":"CVE-2026-40102"},"products":["vikunja"],"published":"2026-04-10","related":[{"cvss_score":9.8,"headline":"Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse","id":"CVE-2026-28268","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":9.1,"headline":"Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change","id":"CVE-2026-27575","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":8.6,"headline":"Vikunja Affected by XSS Via Task Preview","id":"CVE-2026-25935","kev_date_added":null,"published":"2026-02-11"},{"cvss_score":8.3,"headline":"Vikunja Affected by Privilege Escalation via Project Reparenting","id":"CVE-2026-35595","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":8.1,"headline":"Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement","id":"CVE-2026-33316","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.1,"headline":"Vikunja has IDOR in Task Attachment ReadOne Allows Cross-Project File Access and Deletion","id":"CVE-2026-33678","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":7.5,"headline":"Vikunja Vulnerable to Link Share Hash Disclosure via ReadAll Endpoint Enables Permission Escalation","id":"CVE-2026-33680","kev_date_added":null,"published":"2026-03-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-15","vendors":["go-vikunja"]},"summary":"Attackers with scoped API tokens can delete project backgrounds due to method confusion in authorization checks.","url":"https://insights.sbomify.com/CVE-2026-40103/"}