CVE-2026-134272 in Vikunja
Summary
by MITRE • 11/21/2026
Vikunja from 0.9.0 before 2.8.0 contains an information disclosure vulnerability that allows project admins to view share creators' email addresses via the link share list endpoint. Attackers with admin permission can request the project shares endpoint and read the shared_by email field, exposing addresses of creators including former project members.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The identified security flaw within Vikunja versions prior to 2.8.0 represents a significant information disclosure vulnerability that undermines user privacy expectations by exposing personally identifiable information through an administrative interface. This issue specifically affects the link share list endpoint, which is designed to manage shared resources within projects. While the application correctly restricts access to this endpoint based on project administrator privileges, it fails to adequately sanitize or mask sensitive data returned in the API response. Consequently, any user holding admin rights for a specific project can query this endpoint and retrieve detailed metadata about shares created by other users, including their email addresses. This behavior persists even if the sharing individual is no longer an active member of the project, indicating that the system does not properly handle state transitions regarding data visibility when membership status changes.
From a technical perspective, the vulnerability stems from insufficient access control logic and poor data handling practices within the backend API implementation. The server processes requests for share information without verifying whether the exposed fields should remain visible based on current user roles or privacy policies. By returning the shared_by email field directly in the response payload, the application violates the principle of least privilege regarding data exposure. This flaw allows an attacker who has compromised or been granted administrative access to a project to harvest contact details from both current and former members. The persistence of this data for former members suggests that the system retains historical sharing records without applying appropriate de-identification measures, thereby creating a persistent risk vector even after a user leaves the organization or project group.
The operational impact of this vulnerability is primarily centered on privacy violations and potential social engineering risks. Exposed email addresses can be aggregated to build profiles of individuals associated with specific projects, facilitating targeted phishing attacks or credential stuffing attempts if those emails are linked to other compromised databases. Furthermore, for organizations using Vikunja for sensitive operations, the leakage of internal contact information violates data protection regulations such as GDPR in Europe or CCPA in California, potentially leading to legal and compliance repercussions. The ability to view former members' details exacerbates this risk by expanding the attack surface beyond active personnel, making it difficult for administrators to control who has access to historical communication metadata within their projects.
To mitigate this vulnerability, immediate action is required to upgrade Vikunja to version 2.8.0 or later, where these issues have been addressed in subsequent releases. In environments where upgrading is not immediately feasible, organizations should implement strict network-level controls to restrict access to the affected API endpoints only from trusted internal networks and ensure that administrative accounts are protected with multi-factor authentication to reduce the likelihood of unauthorized admin access. Additionally, reviewing project sharing policies and limiting the scope of who can be granted administrator rights will help minimize exposure. Developers must also audit other endpoints for similar information disclosure flaws, ensuring that all sensitive fields like email addresses are masked or omitted in API responses unless explicitly required by business logic and authorized user roles. This incident highlights the critical importance of rigorous input validation and output encoding practices in web applications to prevent unintended data leakage through administrative interfaces.