cve.bz

CVE-2026-111921 go-vikunja vikunja: Incorrect Authorization

5.3 mediumEPSS 0.2%Fix available

Medium (5.3) in go-vikunja vikunja. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in code.vikunja.io/api 2.7.0.

On this page
Vikunja 0.13.0 before 2.7.0 contains an incorrect authorization vulnerability that allows project members with Write permission to delete admin-tier link shares because the delete permission check reads an unloaded share object. Attackers can send DELETE requests to the v1 or v2 projects shares endpoints with sequential share IDs to revoke admin links and invalidate existing share sessions.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • code.vikunja.io/api (Go): fixed in 2.7.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-111921 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111921?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111921?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111921 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
go-vikunja vikunjafrom 0.13.0 before 2.7.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fmmf-xq98-g327Gocode.vikunja.io/api>=0.13.0 <2.7.02.7.0
GO-2026-6730Gocode.vikunja.io/apiall versionsno fix published

References

Check your stackJSON