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.
CVE-2026-91973
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 48%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vikunja-before-2.6.0-authentication-bypass-via-caldav-basicauthCalDAV and feeds BasicAuth endpoints have no rate limit, bypassing the anti-brute-force floor on account passwords · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-m469-88xx-8rx2Vendor Advisories for CVE-2026-91973(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 17:49 UTCEG score recompute
- 2026-09-19 17:49 UTCGHSA enrichment
- 2026-09-19 06:22 UTCEG score recompute
- 2026-09-19 06:22 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:56 UTCGHSA enrichment
- 2026-09-18 07:29 UTCGHSA enrichment
- 2026-09-17 20:02 UTCEG score recompute
- 2026-09-17 20:02 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 08:33 UTCGHSA enrichment
- 2026-09-16 21:07 UTCGHSA enrichment
- 2026-09-16 15:34 UTCEG score recompute
- 2026-09-16 15:34 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 04:01 UTCEG score recompute
- 2026-09-16 04:01 UTCGHSA enrichment
- 2026-09-15 16:32 UTCEG score recompute
- 2026-09-15 16:03 UTCEG score recompute
- 2026-09-15 15:23 UTCEG score recompute
- 2026-09-15 15:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-307
Frequently asked(5)
What is CVE-2026-91973?
When was CVE-2026-91973 disclosed?
Is CVE-2026-91973 actively exploited?
What is the CVSS score of CVE-2026-91973?
How do I remediate CVE-2026-91973?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91973
Is Your Infrastructure Affected by CVE-2026-91973?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.