Vikunja before 2.7.1 Information Disclosure via Team Self-Removal Endpoint
Affects Vikunja 2.7.0 and earlier, where authenticated users can probe team IDs to see whether private teams exist. Fixed in 2.7.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is Vikunja (code.vikunja.io/api) version 2.7.0 or earlier Attacker must be an authenticated user
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.22% · 12th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vikunja before 2.7.1 contains an information disclosure vulnerability that allows authenticated users to determine whether private teams exist by calling the team member self-removal endpoint. Attackers can send DELETE requests to /teams/{id}/members/{own username} for arbitrary team ids and use the distinguishable responses to learn if a team exists, is SSO-managed, or has a single member.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected product is Vikunja (code.vikunja.io/api) version 2.7.0 or earlier Attacker must be an authenticated userUpgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123517
Is CVE-2026-123517 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can probe team IDs to learn whether a private team exists, whether it is SSO-managed, and whether it has a single member. No team names, members, or contents are disclosed, and no data changes.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-123517?
vikunja: before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja (code.vikunja.io/api) versions 2.7.0 and earlier are affected, and the issue involves authenticated users. Compare the installed Vikunja version against that range.Source: github.com, vulncheck.com
How do I fix CVE-2026-123517?
Upgrade to Vikunja 2.7.1 or later, which contains the fix. No workaround is listed in the facts.Source: github.com, vulncheck.com