# CVE-2026-25935: Vikunja Affected by XSS Via Task Preview

> A malicious user can trigger cross-site scripting in Vikunja by sharing a project with a crafted task description, potentially leading to code execution or account takeover.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** GHSA-m4g2-2q66-vc9v, GO-2026-4480

## What is CVE-2026-25935?

CVE-2026-25935 is a high-severity cross-site scripting vulnerability in go-vikunja vikunja, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vikunja is a todo-app to organize your life. Prior to 1.1.0, TaskGlanceTooltip.vue temporarily creates a div and sets the innerHtml to the description. Since there is no escaping on either the server or client side, a malicious user can share a project, create a malicious task, and cause an XSS on hover. This vulnerability is fixed in 1.1.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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

3 open source packages ship an affected version, including code.vikunja.io/api. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.vikunja.io/api` | Go | All versions | None |
| `code.vikunja.io/api` | Go | All versions to 0.24.6 | None |
| `code.vikunja.io/api` | Go | All versions to 0.24.6 | None |

Products: Vikunja Vikunja.

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

Upgrade to a fixed version.

## Is CVE-2026-25935 being exploited?

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

## Other vulnerabilities in go-vikunja vikunja

- [CVE-2026-28268](https://insights.sbomify.com/CVE-2026-28268/): Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse (critical 9.8)
- [CVE-2026-27575](https://insights.sbomify.com/CVE-2026-27575/): Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change (critical 9.1)
- [CVE-2026-35595](https://insights.sbomify.com/CVE-2026-35595/): Vikunja Affected by Privilege Escalation via Project Reparenting (high 8.3)
- [CVE-2026-33316](https://insights.sbomify.com/CVE-2026-33316/): Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement (high 8.1)
- [CVE-2026-33678](https://insights.sbomify.com/CVE-2026-33678/): Vikunja has IDOR in Task Attachment ReadOne Allows Cross-Project File Access and Deletion (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25935 is a high-severity cross-site scripting vulnerability in go-vikunja vikunja, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25935 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected all versions; no fix listed
- code.vikunja.io/api (Go): affected all versions up to 0.24.6; no fix listed
- code.vikunja.io/api (Go): affected all versions up to 0.24.6; no fix listed

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

## Sources

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

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