Skip to main content

Vikunja CVE-2026-91973

| EUVDEUVD-2026-78649 HIGH
Improper Restriction of Excessive Authentication Attempts (CWE-307)
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Probe internet-facing Vikunja instance
  2. Delivery
    Request /dav, /.well-known, /feeds
  3. Exploit
    Submit unbounded BasicAuth guesses
  4. Install
    No rate limit or lockout triggers
  5. C2
    Valid password guessed for account
  6. Execute
    Authenticate to CalDAV/feed API
  7. Impact
    Read victim tasks and project data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Brute-force prevention, rate limiting
Exploitation Conditions

Exploitation requires a Vikunja deployment below 2.6.0 whose CalDAV/feed endpoints (/dav, /.well-known, /feeds) are reachable by the attacker - typically an instance exposed to the internet or to an untrusted network segment - and at least one account that authenticates with a password guessable from a dictionary or credential list. The attack specifically abuses the absence of rate limiting on that BasicAuth code path, so any deployment where those routes are already throttled by an upstream proxy blunts it. Limits on success: accounts protected by OIDC/SSO or a second factor are not compromised by password guessing alone, the CVSS vector reports no integrity or availability impact (VC:H/VI:N/VA:N), and the attacker gains only the access level of whichever account is cracked. Authentication requirements per the provided vector are unauthenticated (PR:N, UI:N).

Impact

The CVSS 4.0 base vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N) yields 8.7 and reflects unauthenticated, low-complexity, network-reachable exploitation with high confidentiality impact. That score should be read with care: the metric set implies automated, unattended guessing is feasible against any internet-reachable instance, but the practical outcome depends entirely on password strength - a strong-password or SSO/2FA deployment is far less exposed than one with weak or reused passwords. No CISA KEV listing and no public exploit code were provided, and no EPSS score was supplied, so active exploitation status is unconfirmed; the VulnCheck attribution indicates an independent researcher disclosure rather than observed attacks. The absence of VI and VA impact limits blast radius to unauthorized read access of the compromised user's data. Treat this as a genuine priority for internet-exposed instances with password-only auth, but as lower urgency for SSO-protected or internal-only deployments.

Exploit ScenarioDerived

An attacker enumerates internet-facing Vikunja instances and posts high-volume BasicAuth requests to /dav or /.well-known using common username/password dictionaries. Because no rate limiting or lockout triggers, the attacker can keep guessing until a password-only account authenticates, then pulls that user's projects, tasks, and feeds over the CalDAV/feed API. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no privileges or user interaction are needed, making this trivially automatable, though success still hinges on password quality.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 PoC candidate (unverified) Patch available 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 15, 2026

Vikunja instances before 2.6.0 expose CalDAV BasicAuth endpoints (/dav, /.well-known, and /feeds) that are not covered by the application's anti-brute-force controls, letting a remote unauthenticated attacker send an unlimited number of credential-guessing requests. Successful guessing against password-only accounts yields full read access to the victim's tasks, projects, and feeds data. The vendor has released 2.6.0 as the fix; no public exploit code or active exploitation has been confirmed in the supplied intelligence.

RemediationAI

Upgrade Vikunja to 2.6.0 or later, which the vendor confirms contains the fix (patch status: available from vendor). After upgrading, verify that rate limiting and lockout now apply to /dav, /.well-known, and /feeds by replaying failed BasicAuth attempts and confirming throttling. If immediate upgrade is not possible, compensate by placing those three paths behind a reverse proxy with per-IP request throttling and temporary bans (e.g., nginx limit_req plus fail2ban on 401 responses) - accepting that this adds latency and can lock out legitimate CalDAV clients behind shared NAT; restrict /dav, /.well-known, and /feeds to trusted source IP ranges or VPN (side effect: breaks mobile calendar and feed clients on the open internet); and force multi-factor or OIDC/SSO logins so that password guessing alone cannot complete authentication (side effect: requires identity-provider integration and may not cover CalDAV client auth). Also audit logs for distributed 401 patterns against those routes and rotate credentials for any account suspected of compromise. See https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m469-88xx-8rx2.

Affected VersionsENISA

vikunja 0 <2.6.0

Affected Packages

go code.vikunja.io/api fix: 2.6.0
euvd vikunja fix: 2.6.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Vikunja is a self-hosted, open-source task and project management application written in Go that exposes a REST API plus CalDAV and iCalendar-feed surfaces for calendar clients. The affected routes implement HTTP BasicAuth authentication, which transmits base64 credentials on every request and is handled by a separate code path from the main login flow. Because that path lacked the rate-limiting and lockout middleware applied to the standard authentication endpoint, it became an unthrottled credential oracle. The root cause is CWE-307 (Improper Restriction of Excessive Authentication Attempts); the CPE cpe:2.3:a:go-vikunja:vikunja:*:*:*:*:*:*:*:* with the EUVD range 0 to <2.6.0 defines the vulnerable window. The CVSS 4.0 vector reports VC:H but VI:N and VA:N, meaning the demonstrated impact class is credential/confidentiality compromise rather than direct data tampering.

Know when Vikunja gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 7.5 HIGH

Network-reachable BasicAuth guessing with no auth or interaction needed, so PR:N/UI:N/AC:L; only confidentiality is impacted, giving C:H/I:N/A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Sep 15, 2026 - 16:03 EUVD
CVE Published
Sep 15, 2026 - 15:18 cve.org
HIGH 8.7

DescriptionCVE.org

Vikunja before 2.6.0 contains an authentication bypass vulnerability in CalDAV BasicAuth endpoints that lack rate limiting protection. Remote unauthenticated attackers can issue unbounded credential-guessing requests against /dav, /.well-known, and /feeds routes to bypass the instance's anti-brute-force controls and compromise password-only accounts.

Technical POC Analysis

Evidence caveat, read first: the supplied advisory (GHSA-m469-88xx-8rx2) rates this Moderate, carries "CVE ID: No known CVE", and lists affected <= 2.5.0 / patched 2.6.0.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Latest POC

1 PoC candidate from github (unverified)

Sign in to open the public PoC links collected for this CVE.

Threat Intelligence Overview

EPSS Score
0.6%
Top 52% exploitable
Prevalence
Low
self-hosted open-source task manager, niche deployment footprint
Threat Intel
1
1 sources
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

65
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-68582 CRITICAL POC
9.3 Aug 02

Cross-tenant information disclosure in the self-hosted task manager Vikunja (0.24.0 through 2.3.0) lets a holder of any

CVE-2026-27575 CRITICAL POC
9.1 Feb 25

Weak password policy in Vikunja task management before 2.0.0 allows users to set trivially guessable passwords. PoC avai

CVE-2026-68581 HIGH POC
8.6 Aug 02

Principal type confusion in Vikunja (versions 0.22.0-2.3.0) allows an authenticated low-privilege attacker to fully cont

CVE-2026-27616 HIGH POC
7.3 Feb 25

Stored cross-site scripting (XSS) in Vikunja prior to version 2.0.0 allows authenticated attackers to steal authenticati

CVE-2026-27819 HIGH POC
7.2 Feb 25

Vikunja before version 2.0.0 contains a path traversal vulnerability in its backup restoration function that fails to va

CVE-2026-27116 MEDIUM POC
6.1 Feb 25

Vikunja is an open-source self-hosted task management platform. [CVSS 6.1 MEDIUM]

CVE-2026-28268 CRITICAL
9.8 Feb 27

Business logic vulnerability in Vikunja task management platform before 2.1.0 allows incomplete resource cleanup, potent

CVE-2026-56765 CRITICAL
9.3 Jul 10

Instance-wide data breach in Vikunja before 2.2.1 lets remote attackers exfiltrate and destroy every file attachment acr

CVE-2026-34727 CRITICAL
9.1 Apr 10

Vikunja's OIDC callback handler issues a full JWT to any successfully matched user without checking whether that account

CVE-2026-91972 HIGH POC
8.7 Sep 15

Vikunja versions before 2.6.0 ship authentication endpoints under /api/v2 (login, register, password-reset, and OAuth to

CVE-2026-91985 HIGH POC
8.7 Sep 15

Vikunja prior to 2.6.0 leaks the secret hash that backs a project's link shares through its single-share read endpoint,

CVE-2026-57458 HIGH
8.1 Oct 09

Privilege escalation in Vikunja 2.3.0 allows a user who holds a narrowly scoped API token (permissions {"oauth":["author

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy