CVE-2026-105835

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-06. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.4Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
33
EG Risk 33/100CISA SSVC

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 computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 6, 2026

Last Modified

October 9, 2026

Advisory Details (4)

Auto-updated Oct 6, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

PLANKA 2.2.0 through 2.2.1 TOTP Brute Force via verify-totp Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/planka-2.2.0-through-2.2.1-totp-brute-force-via-verify-totp-endpoint
generic

GitHub - plankanban/planka: Elegant open source project tracking. Self-hosted Kanban for teams — free Community edition, with PLANKA Pro for organisations. · GitHub

https://github.com/plankanban/planka
generic

planka/server/api/controllers/access-tokens/verify-totp.js at v2.2.1 · plankanban/planka · GitHub

https://github.com/plankanban/planka/blob/v2.2.1/server/api/controllers/access-tokens/verify-totp.js
github_commit

commit de4d76883178 (plankanban/planka)

Fix landed in plankanban/planka commit de4d76883178 — awaiting tagged release

https://github.com/plankanban/planka/commit/de4d7688317829e2a0b665fe9dbf39eaf127b6f9

Vendor Advisories for CVE-2026-105835(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 20× in last 7d / 20× 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.

  1. 2026-10-10 02:20 UTCEG score recompute
  2. 2026-10-10 02:20 UTCGHSA enrichment
  3. 2026-10-09 20:06 UTCEPSS rescore
  4. 2026-10-09 14:21 UTCGHSA enrichment
  5. 2026-10-09 02:19 UTCEG score recompute
  6. 2026-10-09 02:19 UTCGHSA enrichment
  7. 2026-10-09 01:29 UTCEG score recompute
  8. 2026-10-09 01:28 UTCGHSA enrichment
  9. 2026-10-08 17:11 UTCEPSS rescore
  10. 2026-10-08 16:20 UTCGHSA enrichment
  11. 2026-10-08 04:19 UTCEG score recompute
  12. 2026-10-08 04:19 UTCGHSA enrichment
  13. 2026-10-07 23:47 UTCEPSS rescore
  14. 2026-10-07 16:20 UTCGHSA enrichment
  15. 2026-10-07 04:18 UTCGHSA enrichment
  16. 2026-10-06 16:20 UTCEG score recompute
  17. 2026-10-06 16:20 UTCGHSA enrichment
  18. 2026-10-06 13:29 UTCEG score recompute
  19. 2026-10-06 13:04 UTCEG score recompute
  20. 2026-10-06 13:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-105835?
CVE-2026-105835 is a high vulnerability published on October 6, 2026. 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…
When was CVE-2026-105835 disclosed?
CVE-2026-105835 was first published on October 6, 2026, with the most recent update on October 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-105835 actively exploited?
CVE-2026-105835 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105835?
CVE-2026-105835 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105835?
An upstream fix for CVE-2026-105835 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-105835 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-105835

Explore →

Is Your Infrastructure Affected by CVE-2026-105835?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs