Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Vikunja has TOTP Reuse During Validity Window

CVSS 3.1 5.7 MEDIUMEUVD CVSS 3.1 5.7 CVSS 3.1 · [email protected] · Secondary 5.7 MEDIUMCVSS_V3 Publisher rating MODERATEosv · severity unknownCheck source for fixed versionsKEV status unknown

cve-program · CVE-2026-33473

Published

Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue.

Read the publisher's advisory

euvd · EUVD-2026-20081

Published

Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue.

Read the publisher's advisory

nvd · CVE-2026-33473

Published

Vikunja is an open-source self-hosted task management platform. Starting in version 0.13 and prior to version 2.2.1, any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. Version 2.2.1 patches the issue.

Read the publisher's advisory

osv · GHSA-p747-qc5p-773r

Published

### Summary Any user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window. ### Details The below code is called when a user that has 2FA is authenticating to the application. Once they submit a valid username-password-totp combination, the user gets authenticated. If that same TOTP is used for the same user's account again within the validity window, it will allow the other session to authenticate successfully. **Source**: <ins>pkg/user/totp.go:128</ins> ```go // ValidateTOTPPasscode validated totp codes of users. func ValidateTOTPPasscode(s *xorm.Session, passcode *TOTPPasscode) (t *TOTP, err error) { t, err = GetTOTPForUser(s, passcode.User) if err != nil { return } if !totp.Validate(passcode.Passcode, t.Secret) { return nil, ErrInvalidTOTPPasscode{Passcode: passcode.Passcode} } return } ``` Section 6.5.1 within the [Authentication](https://github.com/OWASP/ASVS/blob/master/5.0/en/0x15-V6-Authentication.md) section of the OWASP ASVS recommends multiple checks, some of which involving TOTPs: > Verify that lookup secrets, out-of-band authentication requests or codes, and time-based one-time passwords (TOTPs) are only successfully usable once. The OWASP WSTG also references this as one of their [checks](https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/04-Authentication_Testing/11-Testing_Multi-Factor_Authentication) to look for: > Can the OTPs be used more than once? ### PoC https://github.com/user-attachments/assets/19d3b4c3-c219-4f59-b57d-45c9f6a264c8 ### Impact Any user who uses 2FA could be impacted if their traffic is able to be captured, they're phished/social engineered, or other methods of attack. This disrupts one layer of the defense-in-depth model surrounding 2FA. ### Similar CVEs - [CVE-2025-6014](https://nvd.nist.gov/vuln/detail/CVE-2025-6014) - [CVE-2025-55003](https://nvd.nist.gov/vuln/detail/CVE-2025-55003) ### Remediation Store a deny-list of TOTP codes for their validity windows and check submitted codes against it to ensure none are being reused. After their validity window has closed, the 2FA code can be removed from the list.

Read the publisher's advisory

osv · GO-2026-4805

Published

Vikunja has TOTP Reuse During Validity Window in code.vikunja.io/api. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: .

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current