CVE-2026-59097: Missing Authorization in taiga taiga-back
Taiga before 6.10.2 contains a missing authorization vulnerability that allows unauthenticated remote attackers to create default due-date records in any project by exploiting unprotected POST endpoints on the user-story, task, and issue due-date API viewsets. Attackers can supply an arbitrary project identifier to these endpoints, which bypass permission checks and apply the AllowAny default, to pre-empt project administrators from initializing due dates by creating records before they can do so themselves.
AI Analysis
Technical Summary
CVE-2026-59097 describes a missing authorization vulnerability in Taiga before version 6.10.2. The vulnerability exists in the taiga-back service where certain POST API endpoints related to due-date management for user stories, tasks, and issues do not enforce proper permission checks. Instead, these endpoints apply an AllowAny default, enabling unauthenticated remote attackers to create due-date records in any project by supplying arbitrary project identifiers. This bypasses intended authorization controls and can disrupt project management workflows.
Potential Impact
The vulnerability allows unauthenticated attackers to create or pre-empt due-date records in projects they do not have access to. While it does not disclose sensitive data or allow direct modification of existing data, it impacts the integrity of project scheduling by allowing unauthorized insertion of due dates. There is no impact on confidentiality or availability reported. The CVSS score of 5.3 reflects a medium severity with low attack complexity and no privileges required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects versions prior to 6.10.2, upgrading to version 6.10.2 or later is recommended once a fix is available. Until then, restrict access to the affected API endpoints if possible or implement additional access controls to prevent unauthenticated POST requests to due-date endpoints.
CVE-2026-59097: Missing Authorization in taiga taiga-back
Description
Taiga before 6.10.2 contains a missing authorization vulnerability that allows unauthenticated remote attackers to create default due-date records in any project by exploiting unprotected POST endpoints on the user-story, task, and issue due-date API viewsets. Attackers can supply an arbitrary project identifier to these endpoints, which bypass permission checks and apply the AllowAny default, to pre-empt project administrators from initializing due dates by creating records before they can do so themselves.
CVSS v3.1
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-59097 describes a missing authorization vulnerability in Taiga before version 6.10.2. The vulnerability exists in the taiga-back service where certain POST API endpoints related to due-date management for user stories, tasks, and issues do not enforce proper permission checks. Instead, these endpoints apply an AllowAny default, enabling unauthenticated remote attackers to create due-date records in any project by supplying arbitrary project identifiers. This bypasses intended authorization controls and can disrupt project management workflows.
Potential Impact
The vulnerability allows unauthenticated attackers to create or pre-empt due-date records in projects they do not have access to. While it does not disclose sensitive data or allow direct modification of existing data, it impacts the integrity of project scheduling by allowing unauthorized insertion of due dates. There is no impact on confidentiality or availability reported. The CVSS score of 5.3 reflects a medium severity with low attack complexity and no privileges required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects versions prior to 6.10.2, upgrading to version 6.10.2 or later is recommended once a fix is available. Until then, restrict access to the affected API endpoints if possible or implement additional access controls to prevent unauthenticated POST requests to due-date endpoints.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-02T15:38:18.929Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a46c86427e9c79719043947
Added to database: 07/02/2026, 20:21:56 UTC
Last enriched: 07/17/2026, 09:08:12 UTC
Last updated: 08/16/2026, 00:41:14 UTC
Views: 88
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.