# CVE-2026-105411: Missing authorization in Tuleap Enterprise Edition

> An attacker with tracker admin rights can modify or delete fields across all trackers due to improper authorization checks.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-7mq4-94pv-v7wq

## What is CVE-2026-105411?

CVE-2026-105411 is a high-severity missing authorization vulnerability in Dassault Systèmes Tuleap Enterprise Edition, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Authorization Bypass Through User-Controlled Key vulnerability affecting Tuleap Enterprise Edition from 17.0 through 17.5 could allow an attacker with tracker administration rights on one tracker to update or delete fields of all the trackers on the instance.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-105411 being exploited?

There is no known exploitation of CVE-2026-105411 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105411 is a high-severity missing authorization vulnerability in Dassault Systèmes Tuleap Enterprise Edition, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105411 in the wild and no public exploit code.

Affected product: Dassault Systèmes Tuleap Enterprise Edition. 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-105411/ (Markdown: https://insights.sbomify.com/CVE-2026-105411/index.md)
```

## Sources

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

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