CVE-2026-123513 Vikunja before 2.7.1 Auth Token Leak via API URL Change
High 7.6
Published
Updated
Check this codebase for CVE-2026-123513 and fix it if it is affected.
What it is: CVE-2026-123513 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-123513 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-123513/ (Markdown: https://insights.sbomify.com/CVE-2026-123513/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-123513?
CVE-2026-123513 is a high-severity vulnerability in go-vikunja vikunja, published on 8 Nov 2026.
Official description
Vikunja before 2.7.1 contains a credential exposure vulnerability that allows attackers to steal stored auth tokens by inducing users to switch the frontend API URL. Because checkAndSetApiUrl leaves origin-independent localStorage tokens in place, the bearer token and desktop OAuth refresh token are sent to the attacker's server, enabling account takeover.
Weakness: CWE-201
Which versions are affected by CVE-2026-123513?
How do I fix CVE-2026-123513?
No fix has been published for CVE-2026-123513 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-123513 being exploited?
There is no known exploitation of CVE-2026-123513 in the wild and no public exploit code.
Sources
Also known as GHSA-h52v-3vxf-m2vc, GHSA-rj93-wmch-2crq.