CVE-2026-91980
mediumvikunja before 2.6.0 fails to validate team access when attaching teams to projects, allowing authenticated users to enumerate all teams and members.
vikunja before 2.6.0 fails to validate team access when attaching teams to projects, allowing authenticated users to enumerate all teams and members. Attackers can attach arbitrary team IDs via the project teams endpoint to retrieve complete team rosters including member names and admin flags for unauthorized teams.
CVSS
4.3
4.3 (CVSS v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Severity source: NVD CVSS v3.1 (disclosure@vulncheck.com)
Timeline (UTC)
Published: 2026-09-15 16:17
Modified: 2026-09-16 19:49
NVD status: Deferred
Last synced 2 days ago
Verified against the source API 2026-10-27 06:53 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-39p5-2wrr-xh29 disclosure@vulncheck.com
- https://www.vulncheck.com/advisories/vikunja-before-2.6.0-team-enumeration-via-project-sha... disclosure@vulncheck.com
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-39p5-2wrr-xh29 134c704f-9b21-4f2e-91b3-4a467353bcc0
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 06:53 UTC · record ↗