{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123527 exists.","exposure":"","fix":"No fix has been published for CVE-2026-123527 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123527 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123527 and fix it if it is affected.\n\nWhat it is: CVE-2026-123527 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123527 exists.\n\nAffected product: go-vikunja vikunja. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-123527/ (Markdown: https://insights.sbomify.com/CVE-2026-123527/index.md)","id":"CVE-2026-123527","markdown":"https://insights.sbomify.com/CVE-2026-123527/index.md","name":"CVE-2026-123527","record":{"aliases":["GHSA-j5v7-qcwp-5g32","GHSA-w4rp-qjww-56rf"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delete them via the v2 DELETE background route, and bucket create-only tokens can update existing buckets.","ecosystems":[],"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 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass","id":"CVE-2026-123527","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware","id":"CVE-2026-123528"},"nickname":null,"packages":[],"prev":{"headline":"Vikunja before 2.7.1 Mass Assignment via Team external_id Field","id":"CVE-2026-123526"},"products":["vikunja"],"published":"2026-11-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-11-12","vendors":["go-vikunja"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123527/"}