{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123496 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-123496 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123496 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123496 and fix it if it is affected.\n\nWhat it is: CVE-2026-123496 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123496 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-123496/ (Markdown: https://insights.sbomify.com/CVE-2026-123496/index.md)","id":"CVE-2026-123496","markdown":"https://insights.sbomify.com/CVE-2026-123496/index.md","name":"CVE-2026-123496","record":{"aliases":["GHSA-5mwr-g4r9-hv44","GHSA-rxwp-q2qg-98vw"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Vikunja veans before 2.7.1 contains a symlink following vulnerability that allows attackers to make veans init write files outside the repository via crafted repo symlinks. Attackers can ship symlinked .veans.yml, .claude, or .opencode entries to overwrite user files like ~/.bashrc or install veans hooks and plugins globally.","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 veans before 2.7.1 Symlink Following in veans init","id":"CVE-2026-123496","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 veans before 2.7.1 HTTPS to HTTP Downgrade in Server Discovery","id":"CVE-2026-123497"},"nickname":null,"packages":[],"prev":{"headline":"Vikunja 2.0.0 before 2.7.1 Login CSRF via /api/v2 Login and OIDC Callback","id":"CVE-2026-123495"},"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-12","vendors":["go-vikunja"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123496/"}