# CVE-2026-105835: PLANKA 2.2.0 through 2.2.1 TOTP Brute Force via verify-totp Endpoint

> Attackers can brute force TOTP codes to bypass two-factor authentication and gain full access to user accounts.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-vxgr-w3f5-4g4j

## What is CVE-2026-105835?

CVE-2026-105835 is a critical vulnerability in planka, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 two-factor authentication codes. Attackers who know a user's password can reuse the ten-minute pending token to guess six-digit codes until one succeeds, obtaining a full access token.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-105835?


## How do I fix CVE-2026-105835?

No fix has been published for CVE-2026-105835 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105835 being exploited?

There is no known exploitation of CVE-2026-105835 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105835 and fix it if it is affected.

What it is: CVE-2026-105835 is a critical vulnerability in planka, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105835 in the wild and no public exploit code.

Affected product: planka. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105835/ (Markdown: https://insights.sbomify.com/CVE-2026-105835/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105835
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105835
- OSV: https://osv.dev/vulnerability/CVE-2026-105835

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105835/
Summaries are generated and may contain mistakes; the official description above is the record.