CVE-2026-123517
Deferred Deferred - Pending Action

Information Disclosure in Vikunja Prior to 2.7.1

Vulnerability report for CVE-2026-123517, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-08

Last updated on: 2026-11-08

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-08
Last Modified
2026-11-08
Generated
2026-11-08
AI Q&A
2026-11-08
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
vikunja vikunja to 2.7.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-204 The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-123517 is an information disclosure vulnerability in Vikunja versions before 2.7.1. Authenticated users can exploit the team member self-removal endpoint to check if private teams exist by sending DELETE requests to /teams/{id}/members/{own username} with arbitrary team IDs. The responses reveal whether the team exists, is SSO-managed, or has a single member.

Detection Guidance

To detect this vulnerability, monitor network traffic for DELETE requests to /teams/{id}/members/{own username} endpoints with arbitrary team IDs. Check for distinguishable responses like 412 for SSO-managed teams, last-member errors, or 200 with no deletion. Use tools like curl to test endpoints: curl -X DELETE -H 'Authorization: Bearer <token>' https://<vikunja-server>/teams/<arbitrary-id>/members/<username>

Inspect server logs for repeated unauthorized access attempts to team endpoints. Enable detailed logging for the Vikunja application to capture response codes and payloads for analysis.

Impact Analysis

An attacker could use this to gather intelligence about private teams in a Vikunja instance. While no sensitive data like team names or member lists is exposed, the ability to confirm team existence may aid in further attacks, such as targeted phishing or social engineering.

Compliance Impact

This vulnerability may impact compliance by exposing information about private team structures, potentially violating data protection principles under GDPR or HIPAA. However, no direct disclosure of personal data occurs, so the impact depends on specific regulatory interpretations.

Mitigation Strategies

Immediately update Vikunja to version 2.7.1 or later to patch the vulnerability. If updating is not possible, restrict access to the /teams/{id}/members/{own username} endpoint by implementing stricter authorization checks or network-level controls.

Review and audit all team-related endpoints for similar authorization flaws. Monitor for any signs of exploitation and rotate authentication tokens if unauthorized access is suspected.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-123517. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...