# CVE-2026-65055: Taiga taiga-back Private Project Member Roster Disclosure via Unauthenticated filters_data Endpoints

> Unauthenticated attackers can disclose private project member rosters and workflow configurations via filters_data endpoints in Taiga.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-rj5p-xwjf-qw97

## What is CVE-2026-65055?

CVE-2026-65055 is a medium-severity missing authorization vulnerability in taiga-back, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Taiga 6.10.1 contains a missing authorization vulnerability that allows unauthenticated attackers to disclose the full member roster and internal workflow configuration of any private project by supplying a project ID to the filters_data API endpoints on UserStory, Task, Issue, and Epic viewsets. Attackers can send unauthenticated GET requests to the filters_data endpoints with sequential integer project IDs to enumerate private project membership details including user IDs, full names, and gravatar hashes, bypassing the access controls that correctly restrict other project API endpoints.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-65055?


## How do I fix CVE-2026-65055?

No fix has been published for CVE-2026-65055 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-65055 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65055 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65055 and fix it if it is affected.

What it is: CVE-2026-65055 is a medium-severity missing authorization vulnerability in taiga-back, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65055 exists.

Affected product: taiga-back. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65055/ (Markdown: https://insights.sbomify.com/CVE-2026-65055/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65055
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65055
- OSV: https://osv.dev/vulnerability/CVE-2026-65055

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65055/
Summaries are generated and may contain mistakes; the official description above is the record.