CVE-2026-65055: Missing Authorization in Taiga taiga-back
Taiga version 6.10.1 has a missing authorization vulnerability in its taiga-back component. This flaw allows unauthenticated attackers to access the full member roster and internal workflow configuration of any private project by querying the filters_data API endpoints with a project ID. The vulnerability enables attackers to enumerate private project membership details such as user IDs, full names, and gravatar hashes, bypassing intended access controls. No patch or official remediation has been indicated yet. The CVSS score is 6.9, categorizing it as a medium severity issue.
AI Analysis
Technical Summary
CVE-2026-65055 describes a missing authorization vulnerability in Taiga 6.10.1's taiga-back service. Unauthenticated attackers can send GET requests to the filters_data API endpoints on UserStory, Task, Issue, and Epic viewsets with sequential project IDs to retrieve sensitive information about private projects. This includes the full member roster and internal workflow configuration, which should be protected by access controls. The vulnerability arises because these specific endpoints do not enforce proper authorization checks, unlike other project API endpoints. No vendor advisory or patch information is currently available.
Potential Impact
The vulnerability allows unauthorized disclosure of sensitive project data, including membership details and internal workflow configurations of private projects. This exposure can lead to privacy violations and potential reconnaissance for further attacks. However, it does not allow modification or deletion of data, nor does it provide direct system control. The CVSS 4.0 vector indicates network attack vector, low complexity, no privileges or user interaction required, and low impact on confidentiality only.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the affected API endpoints if possible, and monitor for unusual access patterns. Avoid exposing project IDs publicly to reduce the risk of enumeration. Follow updates from the Taiga project for official fixes or workarounds.
CVE-2026-65055: Missing Authorization in Taiga taiga-back
Description
Taiga version 6.10.1 has a missing authorization vulnerability in its taiga-back component. This flaw allows unauthenticated attackers to access the full member roster and internal workflow configuration of any private project by querying the filters_data API endpoints with a project ID. The vulnerability enables attackers to enumerate private project membership details such as user IDs, full names, and gravatar hashes, bypassing intended access controls. No patch or official remediation has been indicated yet. The CVSS score is 6.9, categorizing it as a medium severity issue.
CVSS v4.0
Score 6.9medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-65055 describes a missing authorization vulnerability in Taiga 6.10.1's taiga-back service. Unauthenticated attackers can send GET requests to the filters_data API endpoints on UserStory, Task, Issue, and Epic viewsets with sequential project IDs to retrieve sensitive information about private projects. This includes the full member roster and internal workflow configuration, which should be protected by access controls. The vulnerability arises because these specific endpoints do not enforce proper authorization checks, unlike other project API endpoints. No vendor advisory or patch information is currently available.
Potential Impact
The vulnerability allows unauthorized disclosure of sensitive project data, including membership details and internal workflow configurations of private projects. This exposure can lead to privacy violations and potential reconnaissance for further attacks. However, it does not allow modification or deletion of data, nor does it provide direct system control. The CVSS 4.0 vector indicates network attack vector, low complexity, no privileges or user interaction required, and low impact on confidentiality only.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the affected API endpoints if possible, and monitor for unusual access patterns. Avoid exposing project IDs publicly to reduce the risk of enumeration. Follow updates from the Taiga project for official fixes or workarounds.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-21T14:05:53.720Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5fdfa89c2644c7f8c1b07c
Added to database: 07/21/2026, 21:07:52 UTC
Last enriched: 07/30/2026, 05:21:19 UTC
Last updated: 09/04/2026, 10:52:10 UTC
Views: 69
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.