VulnerabilityPublished 25 Feb 2026

CVE-2026-27575: vikunja · Weak Password Requirements

Affects vikunjaSource CVE Database V5

Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.0.0 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.0.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vikunja and github.com/go-vikunja/vikunja to 2.0.0.

Affected software

Product	Affected	Fixed in
go-vikunjavikunja	Affected <2.0.0	Fixed in 2.0.0
Gogithub.com/go-vikunja/vikunja`pkg:golang/github.com/go-vikunja/vikunja`Other threats	Affected <2.0.0	Fixed in 2.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade Vikunja to version 2.0.0 or later to benefit from enforced strong password policies and session invalidation upon password changes. Until upgrading, administrators should enforce strong password policies manually, such as requiring minimum length, complexity, and prohibiting common passwords. Implement rate limiting and account lockout mechanisms to mitigate brute-force attacks. Monitor authentication logs for suspicious login attempts and unusual session activity. Encourage users to enable multi-factor authentication (MFA) if supported by Vikunja or the hosting environment to add an additional layer of security. Regularly audit active sessions and forcibly terminate sessions when suspicious activity is detected or after password resets. Network segmentation and limiting Vikunja access to trusted IP ranges can reduce exposure. Finally, educate users about the risks of weak passwords and credential reuse.

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.

Impact

This vulnerability poses a severe risk to organizations using Vikunja versions prior to 2.0.0. Attackers can exploit weak password policies to gain unauthorized access through brute-force or credential stuffing attacks. Once access is obtained, the failure to invalidate active sessions after password changes allows attackers to maintain persistent access, bypassing user attempts to secure their accounts. This can lead to unauthorized disclosure of sensitive task management data, manipulation or deletion of tasks, and potential lateral movement within an organization's network if Vikunja is integrated with other systems. The confidentiality and integrity of organizational data are at high risk, potentially resulting in operational disruption, loss of trust, and compliance violations. Since Vikunja is self-hosted, the impact depends on the security posture of the hosting environment, but the vulnerability significantly lowers the barrier for attackers to compromise accounts.

CWE-521Weak Password Requirements (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not require that users should have strong passwords.
Architecture and Design
A product's design should require adherence to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes: Enforcement of a minimum and maximum length; Restrictions against password reuse; Restrictions against using…
Architecture and Design
Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
Implementation
Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.1.2 (opens in a new tab)
V2.1.4 (opens in a new tab)
V2.1.3 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Kerberoasting (opens in a new tab)
Rainbow Table Password Cracking (opens in a new tab)
Remote Services with Stolen Credentials (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-613DEPRECATED: Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This entry has been deprecated because it was insufficiently clear. Consider CWE-1462 and its descendants.
MITRE does not allow mapping vulnerabilities to this entry; it groups weaknesses rather than naming one.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Mar 2026, 09:58 UTC

WeaknessesCWE-521, CWE-613

Technical details

References

Community reviews

Related threats