# CVE-2026-123494: Vikunja before 2.7.1 Login CSRF via Migration OAuth Callbacks


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/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-vv55-5rp5-mff9, GHSA-xgw3-ccqg-f6ww

## What is CVE-2026-123494?

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

### Official description

Vikunja before 2.7.1 contains a cross-site request forgery vulnerability that allows attackers to import their data into a victim's account because the Todoist, Microsoft To Do, and Trello migration OAuth callbacks lack a bound state parameter. Attackers can authorize their own account, keep the unused callback code or token, and lure a logged-in victim to the migration callback route to auto-import attacker-chosen projects and tasks containing phishing links.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-123494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123494 is a medium-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123494 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-123494/ (Markdown: https://insights.sbomify.com/CVE-2026-123494/index.md)
```

## Sources

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

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