{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123517 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-123517 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123517 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123517 and fix it if it is affected.\n\nWhat it is: CVE-2026-123517 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123517 in the wild and no public exploit code.\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-123517/ (Markdown: https://insights.sbomify.com/CVE-2026-123517/index.md)","id":"CVE-2026-123517","markdown":"https://insights.sbomify.com/CVE-2026-123517/index.md","name":"CVE-2026-123517","record":{"aliases":["GHSA-cwvj-xw34-46qv","GHSA-v3r6-33v3-79c2"],"analysis":null,"analysis_generated_by":null,"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-204","name":"Observable Response Discrepancy"}],"description":"Vikunja before 2.7.1 contains an information disclosure vulnerability that allows authenticated users to determine whether private teams exist by calling the team member self-removal endpoint. Attackers can send DELETE requests to /teams/{id}/members/{own username} for arbitrary team ids and use the distinguishable responses to learn if a team exists, is SSO-managed, or has a single member.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Vikunja before 2.7.1 Information Disclosure via Team Self-Removal Endpoint","id":"CVE-2026-123517","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 Missing Authorization in Kanban Task-Bucket Move","id":"CVE-2026-123518"},"nickname":null,"packages":[],"prev":{"headline":"Vikunja before 2.7.1 Resource Exhaustion via Vikunja-File ZIP Import","id":"CVE-2026-123516"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-10","vendors":["go-vikunja"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123517/"}