Skip to main content

PLANKA 2.2.0 through 2.2.1 fails to limit incorrect TOTP codes submitted to POST /api/access-tokens/verify-totp, allowing attackers to brute force… (CVE-2026-105835)

0
Critical
Published: 10/06/2026 (10/06/2026, 15:31:56 UTC)
Source: GCVE Database

Description

PLANKA versions 2.2.0 and 2.2.1 contain a vulnerability in the two-factor authentication process where the system fails to limit the number of incorrect TOTP codes submitted to the verification endpoint. This allows an attacker who already knows a user's password to brute force the six-digit TOTP codes by reusing a valid pending token within a ten-minute window, potentially obtaining a full access token.

CVSS v3.1

Score 7.4high

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected software

GitHub Actionsmore threats →ai
plankanban/planka
pkg:github/plankanban/planka
Affected versions
=2.2.0=2.2.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/06/2026, 16:49:13 UTC

Technical Analysis

PLANKA versions 2.2.0 and 2.2.1 do not enforce rate limiting or other restrictions on incorrect TOTP code submissions to the POST /api/access-tokens/verify-totp endpoint. An attacker with knowledge of a user's password can reuse the ten-minute pending token to repeatedly guess six-digit TOTP codes until successful, bypassing two-factor authentication and gaining full access tokens. This vulnerability is identified as CVE-2026-105835 and is associated with CWE-307 (Improper Restriction of Excessive Authentication Attempts).

Potential Impact

Successful exploitation allows attackers who know a user's password to bypass two-factor authentication by brute forcing the TOTP code, resulting in unauthorized access with full access tokens. This compromises confidentiality and integrity of user accounts but does not affect availability.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the affected endpoint, monitor for suspicious authentication attempts, and consider additional protective controls such as IP rate limiting or multi-factor authentication methods that are not vulnerable to brute force attacks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-vxgr-w3f5-4g4j
Osv Schema Version
1.4.0
Aliases
["CVE-2026-105835"]
Database Specific Severity
CRITICAL
Cvss Version
3.1

Threat ID: 6ac523732cdf04f656c4bf30

Added to database: 10/06/2026, 16:36:03 UTC

Last enriched: 10/06/2026, 16:49:13 UTC

Last updated: 10/06/2026, 16:49:13 UTC

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses