# CVE-2026-123500: Vikunja before 2.7.1 Insecure Permissions on Dump Archive via vikunja dump


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-fgfv-xjh6-9vhx, GHSA-rp64-xg8g-9mpr

## What is CVE-2026-123500?

CVE-2026-123500 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 

### Official description

Vikunja before 2.7.1 contains an insecure file permissions vulnerability that allows local users to read dump archives created with umask permissions by the vikunja dump command. Local attackers on a shared host can read the world-readable zip in the rootpath to obtain config, password hashes, TOTP secrets, tokens, and stored files.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-123500?


## How do I fix CVE-2026-123500?

No fix has been published for CVE-2026-123500 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123500 being exploited?

There is no known exploitation of CVE-2026-123500 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123500 and fix it if it is affected.

What it is: CVE-2026-123500 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123500 in the wild and no public exploit code.

Affected product: go-vikunja vikunja. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123500/ (Markdown: https://insights.sbomify.com/CVE-2026-123500/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123500
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123500
- OSV: https://osv.dev/vulnerability/CVE-2026-123500

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123500/
Summaries are generated and may contain mistakes; the official description above is the record.