Vikunja before 2.6.0 fails to properly restrict access to the link-share hash field in single-share read endpoints, allowing read-only members to obtain the share's secret credential. Attackers can exchange the disclosed hash for a link-share JWT at the share's permission level to escalate privileges and perform unauthorized writes or administrative actions.
CVE-2026-91985
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Vikunja before 2.6.0 Privilege Escalation via Link Share Hash | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vikunja-before-2.6.0-privilege-escalation-via-link-share-hashRead-only project members can obtain any link share's access hash via the single-share read endpoint (v1 and v2) and escalate to the share's permission level · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-qfwc-vx6f-3g6gVendor Advisories for CVE-2026-91985(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 28× in last 7d / 43× 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-25 07:06 UTCGHSA enrichment
- 2026-09-24 19:52 UTCEG score recompute
- 2026-09-24 19:52 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 08:38 UTCGHSA enrichment
- 2026-09-23 21:24 UTCEG score recompute
- 2026-09-23 21:24 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 10:11 UTCGHSA enrichment
- 2026-09-22 22:57 UTCEG score recompute
- 2026-09-22 22:57 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-22 11:42 UTCGHSA enrichment
- 2026-09-22 00:29 UTCEG score recompute
- 2026-09-22 00:29 UTCGHSA enrichment
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 13:14 UTCGHSA enrichment
- 2026-09-21 02:00 UTCEG score recompute
- 2026-09-21 02:00 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 14:46 UTCGHSA enrichment
- 2026-09-20 03:32 UTCGHSA enrichment
- 2026-09-19 16:18 UTCEG score recompute
- 2026-09-19 16:18 UTCGHSA enrichment
- 2026-09-19 05:04 UTCEG score recompute
Show 18 moreShow fewer
- 2026-09-19 05:04 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 17:50 UTCGHSA enrichment
- 2026-09-18 06:36 UTCEG score recompute
- 2026-09-18 06:36 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 19:22 UTCGHSA enrichment
- 2026-09-17 07:13 UTCGHSA enrichment
- 2026-09-16 19:57 UTCGHSA enrichment
- 2026-09-16 16:00 UTCEG score recompute
- 2026-09-16 16:00 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 04:46 UTCEG score recompute
- 2026-09-16 04:46 UTCGHSA enrichment
- 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-91985?
When was CVE-2026-91985 disclosed?
Is CVE-2026-91985 actively exploited?
What is the CVSS score of CVE-2026-91985?
How do I remediate CVE-2026-91985?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91985
Is Your Infrastructure Affected by CVE-2026-91985?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.