# CVE-2026-27575: Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change

> Attackers can maintain persistent access after password resets due to weak password policies and session invalidation failures in Vikunja.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-3ccg-x393-96v8, GO-2026-4551

## What is CVE-2026-27575?

CVE-2026-27575 is a critical vulnerability in go-vikunja vikunja, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vikunja is an open-source self-hosted task management platform. Prior to version 2.0.0, the application allows users to set weak passwords (e.g., 1234, password) without enforcing minimum strength requirements. Additionally, active sessions remain valid after a user changes their password. An attacker who compromises an account (via brute-force or credential stuffing) can maintain persistent access even after the victim resets their password. Version 2.0.0 contains a fix.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-521 (Weak Password Requirements)

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

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-27575?

Upgrade to a fixed version.

## Is CVE-2026-27575 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27575 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-25935](https://insights.sbomify.com/CVE-2026-25935/): Vikunja Affected by XSS Via Task Preview (high 8.6)
- [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-27575 and fix it if it is affected.

What it is: CVE-2026-27575 is a critical vulnerability in go-vikunja vikunja, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27575 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-27575/ (Markdown: https://insights.sbomify.com/CVE-2026-27575/index.md)
```

## Sources

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

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