{"answers":{"affected":"3 open source packages ship an affected version, including code.vikunja.io/api.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111919 exists.","fix":"No fix has been published for CVE-2026-111919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-111919 is a high-severity missing authorization vulnerability in go-vikunja vikunja, published on 17 Oct 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-111919 and fix it if it is affected.\n\nWhat it is: CVE-2026-111919 is a high-severity missing authorization vulnerability in go-vikunja vikunja, published on 17 Oct 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-111919 exists.\n\nAffected packages and fixed versions:\n- code.vikunja.io/api (Go): affected from 0.22.0; no fix listed\n- code.vikunja.io/api (Go): affected from 0.22.0 up to 2.6.0; no fix listed\n- code.vikunja.io/api (Go): affected from 0.22.0 up to 2.6.0; no fix listed\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-111919/ (Markdown: https://insights.sbomify.com/CVE-2026-111919/index.md)","id":"CVE-2026-111919","markdown":"https://insights.sbomify.com/CVE-2026-111919/index.md","name":"CVE-2026-111919","record":{"aliases":["GHSA-276j-w3vx-r5jh","GHSA-hjx8-qv73-f7cm","GO-2026-6733"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Vikunja task manager","requires_auth":"low_privilege","summary":"Removed collaborators can continue receiving sensitive project data via webhooks they created, exposing task details after access revocation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Vikunja 0.22.0 before 2.7.0 contains an improper access revocation vulnerability that allows removed collaborators to keep receiving project data through webhooks they created. Former collaborators keep receiving task titles and descriptions through their webhook, including content created after their access was revoked.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Vikunja 0.22.0 before 2.7.0 Improper Access Revocation via Webhooks","id":"CVE-2026-111919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Vikunja 2.6.0 Broken Access Control via Inherited Project Permissions","id":"CVE-2026-111920"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0.22.0"],"last_affected":[],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GO-2026-6733"},{"ecosystem":"Go","fixed":[],"introduced":["0.22.0"],"last_affected":["2.6.0"],"package":"code.vikunja.io/api","purl":null,"source":"GHSA-hjx8-qv73-f7cm"},{"ecosystem":"Go","fixed":[],"introduced":["0.22.0"],"last_affected":["2.6.0"],"package":"code.vikunja.io/api","purl":"pkg:golang/code.vikunja.io/api","source":"GHSA-hjx8-qv73-f7cm"}],"prev":{"headline":"Vikunja 1.0.0-rc0 before 2.7.0 Cross-Tenant Task Position Writes via Saved Filter Creation","id":"CVE-2026-111918"},"products":["vikunja"],"published":"2026-10-17","related":[],"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":"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-10-19","vendors":["go-vikunja"]},"summary":"Removed collaborators can continue receiving sensitive project data via webhooks they created, exposing task details after access revocation.","url":"https://insights.sbomify.com/CVE-2026-111919/"}