# CVE-2026-123522: Vikunja before 2.7.1 Task Information Disclosure via Kanban Bucket Move Webhook


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-5q33-h98p-rgh9, GHSA-x356-gv6g-6mff

## What is CVE-2026-123522?

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

### Official description

Vikunja before 2.7.1 contains an authorization bypass vulnerability that allows authenticated users to read any task by injecting a crafted task object into a no-op Kanban bucket move. Attackers can set task.id to a victim task and task.project_id to their own project, routing full task contents to their webhook and forging mention notifications.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-123522 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123522 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123522 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123522 exists.

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-123522/ (Markdown: https://insights.sbomify.com/CVE-2026-123522/index.md)
```

## Sources

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

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