Vikunja before 2.6.0 fails to validate that user-supplied project_view_id in task-position requests belongs to the task's project. Authenticated attackers can insert task position rows into arbitrary other tenant project views via POST or PUT task-position endpoints.
CVE-2026-91984
Score 4.3 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 4.3; 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
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Vikunja before 2.6.0 Broken Object-Level Authorization via task-position | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vikunja-before-2.6.0-broken-object-level-authorization-via-task-positionCross-tenant task-position rows can be injected into arbitrary project views via the unvalidated project_view_id in the task position endpoint (v1 and v2) · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-w39f-h553-h2mxVendor Advisories for CVE-2026-91984(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.
- 2026-09-20 23:23 UTCEG score recompute
- 2026-09-20 23:23 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 22:24 UTCEG score recompute
- 2026-09-19 22:24 UTCGHSA enrichment
- 2026-09-18 21:26 UTCEG score recompute
- 2026-09-18 21:26 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:29 UTCEG score recompute
- 2026-09-17 20:29 UTCGHSA enrichment
- 2026-09-17 19:39 UTCEG score recompute
- 2026-09-17 19:39 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 21:07 UTCGHSA enrichment
- 2026-09-16 17:55 UTCEG score recompute
- 2026-09-16 17:55 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-15 16:32 UTCEG score recompute
- 2026-09-15 15:23 UTCEG score recompute
- 2026-09-15 15:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-91984?
When was CVE-2026-91984 disclosed?
Is CVE-2026-91984 actively exploited?
What is the CVSS score of CVE-2026-91984?
How do I remediate CVE-2026-91984?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91984
Is Your Infrastructure Affected by CVE-2026-91984?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.