# CVE-2025-59040: Tuleap backlog item representations do not verify the permissions of the child trackers

> Attackers can view names of trackers they lack permission to access due to missing permission checks in backlog item representations.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 18 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-67xc-39v9-pffg

## What is CVE-2025-59040?

CVE-2025-59040 is a medium-severity missing authorization vulnerability in Enalean tuleap, published on 18 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tuleap is an Open Source Suite to improve management of software developments and collaboration. Backlog item representations do not verify the permissions of the child trackers. Users might see tracker names they should not have access to. This vulnerability is fixed in Tuleap Community Edition 16.11.99.1757427600 and Tuleap Enterprise Edition 16.11-6 and 16.10-8.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2025-59040?


## How do I fix CVE-2025-59040?

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

## Is CVE-2025-59040 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59040 and fix it if it is affected.

What it is: CVE-2025-59040 is a medium-severity missing authorization vulnerability in Enalean tuleap, published on 18 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59040 in the wild and no public exploit code.

Affected product: Enalean tuleap. 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-2025-59040/ (Markdown: https://insights.sbomify.com/CVE-2025-59040/index.md)
```

## Sources

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

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