Vikunja versions before 2.6.0 contain a resource exhaustion vulnerability in the Planka migrator that fails to enforce aggregate memory budgets during migration jobs. Authenticated attackers can submit migration requests pointing to attacker-controlled servers advertising numerous size-compliant attachments, exhausting worker memory and causing denial of service for all users.
CVE-2026-91970
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Vikunja before 2.6.0 Resource Exhaustion via Planka Migration | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vikunja-before-2.6.0-resource-exhaustion-via-planka-migrationPlanka migration retains an unbounded aggregate of attacker-served attachments and can OOM the API · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-wq92-8x3r-fm38Vendor Advisories for CVE-2026-91970(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 17× in last 7d / 17× 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.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 14:14 UTCGHSA enrichment
- 2026-09-19 15:58 UTCEG score recompute
- 2026-09-19 15:57 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 17:39 UTCEG score recompute
- 2026-09-18 17:39 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 19:22 UTCGHSA enrichment
- 2026-09-16 19:57 UTCGHSA enrichment
- 2026-09-16 15:49 UTCEG score recompute
- 2026-09-16 15:49 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-15 17:32 UTCEG score recompute
- 2026-09-15 16:18 UTCEG score recompute
- 2026-09-15 15:23 UTCEG score recompute
- 2026-09-15 15:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-91970?
When was CVE-2026-91970 disclosed?
Is CVE-2026-91970 actively exploited?
What is the CVSS score of CVE-2026-91970?
How do I remediate CVE-2026-91970?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91970
Is Your Infrastructure Affected by CVE-2026-91970?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.