# CVE-2026-59097: Taiga < 6.10.2 - Unauthorized Due-Date Creation via API Viewsets

> Unauthenticated attackers can create due-date records in any project by exploiting unprotected API endpoints, bypassing permission checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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:** 2 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-9rxg-cv94-jvcq

## What is CVE-2026-59097?

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

### Official 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.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-59097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59097 is a medium-severity missing authorization vulnerability in taiga-back, published on 2 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-59097 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-59097/ (Markdown: https://insights.sbomify.com/CVE-2026-59097/index.md)
```

## Sources

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

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