{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123514 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-123514 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123514 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123514 and fix it if it is affected.\n\nWhat it is: CVE-2026-123514 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123514 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-123514/ (Markdown: https://insights.sbomify.com/CVE-2026-123514/index.md)","id":"CVE-2026-123514","markdown":"https://insights.sbomify.com/CVE-2026-123514/index.md","name":"CVE-2026-123514","record":{"aliases":["GHSA-7gmh-4fw6-8xc5","GHSA-hx3f-4c73-rjcc"],"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:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Vikunja before 2.7.1 contains an improper resource cleanup vulnerability that leaves full-data export archives orphaned on disk after re-exports, failed exports, or account deletion. Authenticated users can repeatedly re-trigger exports containing all their attachments to exhaust disk storage, while deleted users' personal data remains retained indefinitely.","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 Orphaned Export Archives Enable Disk Exhaustion","id":"CVE-2026-123514","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 Client-Side Request Forgery via Stored Rich-Text Images","id":"CVE-2026-123515"},"nickname":null,"packages":[],"prev":{"headline":"Vikunja before 2.7.1 Auth Token Leak via API URL Change","id":"CVE-2026-123513"},"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-09","vendors":["go-vikunja"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123514/"}