Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-35597— Vikunja Affected by TOTP Brute-Force Due to Non-Functional Account Lockout

CVSS 5.9 · Medium EPSS 0.04% · P11
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-35597

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Vikunja Affected by TOTP Brute-Force Due to Non-Functional Account Lockout
Source: NVD (National Vulnerability Database)
Vulnerability Description
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the TOTP failed-attempt lockout mechanism is non-functional due to a database transaction handling bug. When a TOTP validation fails, the login handler in pkg/routes/api/v1/login.go calls HandleFailedTOTPAuth and then unconditionally rolls back. HandleFailedTOTPAuth in pkg/user/totp.go uses an in-memory counter (key-value store) to track failed attempts. When the counter reaches 10, it calls user.SetStatus(s, StatusAccountLocked) on the same database session s. Because the login handler always rolls back after a TOTP failure, the StatusAccountLocked write is undone. The in-memory counter correctly increments past 10, so the lockout code executes on every subsequent attempt, but the database write is rolled back every time. This allows unlimited brute-force attempts against TOTP codes. This vulnerability is fixed in 2.3.0.
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Source: NVD (National Vulnerability Database)
Vulnerability Type
过多认证尝试的限制不恰当
Source: NVD (National Vulnerability Database)
Vulnerability Title
Vikunja 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Vikunja是Vikunja开源的一个待办事项应用程序。 Vikunja 2.3.0之前版本存在安全漏洞,该漏洞源于TOTP失败尝试锁定机制因数据库事务处理错误而失效,可能导致对TOTP代码进行无限暴力破解攻击。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
go-vikunjavikunja < 2.3.0 -

II. Public POCs for CVE-2026-35597

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-35597

登录查看更多情报信息。

Same Patch Batch · go-vikunja · 2026-04-10 · 11 CVEs total

CVE-2026-355958.3 HIGHVikunja Affected by Privilege Escalation via Project Reparenting
CVE-2026-347277.4 HIGHVikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path
CVE-2026-355946.5 MEDIUMVikunja Link Share JWT tokens remain valid for 72 hours after share deletion or permission
CVE-2026-355996.5 MEDIUMVikunja has an Algorithmic Complexity DoS in Repeating Task Handler
CVE-2026-356005.4 MEDIUMVikunja has HTML Injection via Task Titles in Overdue Email Notifications
CVE-2026-356025.4 MEDIUMVikunja has a File Size Limit Bypass via Vikunja Import
CVE-2026-355964.3 MEDIUMVikunja has Broken Access Control on Label Read via SQL Operator Precedence Bug
CVE-2026-355984.3 MEDIUMVikunja has Missing Authorization on CalDAV Task Read
CVE-2026-401034.3 MEDIUMVikunja's Scoped API tokens with projects.background permission can delete project backgro
CVE-2026-356014.1 MEDIUMVikunja has an iCalendar Property Injection via CRLF in CalDAV Task Output

IV. Related Vulnerabilities

V. Comments for CVE-2026-35597

No comments yet


Leave a comment