CVE-2026-91969 json
vikunja before 2.6.0 Resource Exhaustion via CSV Migration
published last mo. modified 23d ago also EUVD-2026-78645 , GHSA-pqf9-h8g4-8gmh , GO-2026-6746
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
vikunja versions before 2.6.0 contain a resource exhaustion vulnerability in the POST /api/v2/migration/csv/migrate endpoint that fails to limit parsed row cardinality. Authenticated attackers can upload multipart CSV files with millions of tiny records to exhaust process memory and terminate the API service.
Patch / fix
- go code.vikunja.io/api 2.6.0
- go-vikunja vikunja 2.6.0
- github.com/go-vikunja/vikunja#3688 pull request
- github.com/go-vikunja/vikunja/releases/tag/v2.6.0 release
Is CVE-2026-91969 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.vikunja.io/api | >=2.5.0, <2.6.0 all versions |
2.6.0 |
Affected products
- go-vikunja vikunja
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/go-vikunja/vikunja/pull/3688
web
-
github.com
/go-vikunja/vikunja/security/advisories/GHSA-pqf9-h8g4-8gmh
vendor-advisory, web, advisory
-
vulncheck.com
/advisories/vikunja-before-2.6.0-resource-exhaustion-via-csv-migration
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-91969
advisory
-
github.com
/go-vikunja/vikunja
package
-
github.com
/go-vikunja/vikunja/releases/tag/v2.6.0
web
Sources
- CVE List CVE-2026-91969
- GitHub Advisory GHSA-pqf9-h8g4-8gmh
- NVD CVE-2026-91969
- OSV GO-2026-6746
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.