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

Critical 9.1 Published Updated

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

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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, CWE-521

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.

PackageAffectedFixed in
code.vikunja.io/api GoAll versionsNone
code.vikunja.io/api GoAll versions to 0.24.6None
code.vikunja.io/api GoAll versions to 0.24.6None

Products include 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.

Sources

Also known as GHSA-3ccg-x393-96v8, GO-2026-4551.

Is CVE-2026-27575 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free