Vikunja through 2.4.0 contains a principal-type confusion vulnerability where LinkSharing principals with id N are treated as user principals with users.id == N at three permission checks lacking type guards. Attackers with a link-share JWT can remove victims from teams, enumerate and delete victim bot users, or read team rosters by exploiting id collisions in the autoincrement space.
CVE-2026-76216
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. 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
- 34(Track)EG Risk 34/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Vikunja through 2.4.0 Principal-Type Confusion via LinkSharing | Advisories | VulnCheck
https://www.vulncheck.com/advisories/vikunja-through-principal-type-confusion-via-linksharingLink-share principal-type confusion enables cross-account team removal, bot takeover, and roster disclosure · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-32r8-5843-4qw2Vendor Advisories for CVE-2026-76216(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 13× in last 7d / 13× 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-08-21 04:59 UTCEG score recompute
- 2026-08-21 04:59 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 17:35 UTCEG score recompute
- 2026-08-20 17:35 UTCGHSA enrichment
- 2026-08-20 16:17 UTCEG score recompute
- 2026-08-20 16:17 UTCGHSA enrichment
- 2026-08-20 14:00 UTCGHSA enrichment
- 2026-08-20 01:50 UTCEG score recompute
- 2026-08-20 01:50 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-76216?
When was CVE-2026-76216 disclosed?
Is CVE-2026-76216 actively exploited?
What is the CVSS score of CVE-2026-76216?
How do I remediate CVE-2026-76216?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76216
Is Your Infrastructure Affected by CVE-2026-76216?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.