{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65055 exists.","fix":"No fix has been published for CVE-2026-65055 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-65055 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65055 exists.\n\nAffected product: taiga-back. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-65055/ (Markdown: https://insights.sbomify.com/CVE-2026-65055/index.md)","id":"CVE-2026-65055","markdown":"https://insights.sbomify.com/CVE-2026-65055/index.md","name":"CVE-2026-65055","record":{"aliases":["GHSA-rj5p-xwjf-qw97"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Taiga project management","requires_auth":"none","summary":"Unauthenticated attackers can disclose private project member rosters and workflow configurations via filters_data endpoints in Taiga.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Taiga taiga-back Private Project Member Roster Disclosure via Unauthenticated filters_data Endpoints","id":"CVE-2026-65055","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"mcp-webresearch Server-Side Request Forgery in visit_page Due to Missing Internal-IP Filtering","id":"CVE-2026-65056"},"packages":[],"prev":{"headline":"MediaCMS Private Media Metadata Disclosure via Playlist Ownership Loophole","id":"CVE-2026-65054"},"products":["taiga-back"],"published":"2026-07-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Taiga"]},"summary":"Unauthenticated attackers can disclose private project member rosters and workflow configurations via filters_data endpoints in Taiga.","url":"https://insights.sbomify.com/CVE-2026-65055/"}