# Vikunja: Cross-project task disclosure through subtask expansion

Advisory record · `GHSA-3hc7-r24j-rpwc`

- **Identifiers:** `GHSA-3hc7-r24j-rpwc` · `GO-2026-6714`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 9 Oct 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Oct 2026, 20:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `code.vikunja.io/api` (Go): affected `<2.6.0`; fixed in `2.6.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Vikunja versions before 2.6.0 expose tasks from projects the caller cannot access. When a task list is requested with subtask expansion, linked subtasks are returned without the project-access check applied to the main listing, so a user with read-only access to one project can read full task data from a private project that is linked as a subtask. Upgrade to Vikunja 2.6.0 or later, which applies the same access filter to expanded subtasks.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3hc7-r24j-rpwc)

## Sources

- [GitHub Advisory Database: GHSA-3hc7-r24j-rpwc](https://github.com/advisories/GHSA-3hc7-r24j-rpwc)
- [OSV: GHSA-3hc7-r24j-rpwc](https://osv.dev/vulnerability/GHSA-3hc7-r24j-rpwc)
- <https://github.com/go-vikunja/vikunja/security/advisories/GHSA-3hc7-r24j-rpwc>
- <https://github.com/go-vikunja/vikunja/pull/3688>
- <https://github.com/go-vikunja/vikunja/commit/077dc4de79ce6f1ab59215a2c7bf9b30423685f2>
- <https://github.com/go-vikunja/vikunja>
- <https://github.com/go-vikunja/vikunja/releases/tag/v2.6.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3hc7-r24j-rpwc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3hc7-r24j-rpwc/>. Everything for agents: <https://agentprime.io/llms.txt>.