# CVE-2026-19851: Use of Default Password vulnerability affecting Tuleap Enterprise Edition from 17.0 through 17.5

> Attackers can access user accounts created during XML import due to default passwords in Tuleap Enterprise Edition.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-mcjj-mw6v-j777

## What is CVE-2026-19851?

CVE-2026-19851 is a high-severity vulnerability in Dassault Systèmes Tuleap Enterprise Edition, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Use of Default Password vulnerability affecting Tuleap Enterprise Edition from 17.0 through 17.5 could allow an attacker to gain access to user accounts created during XML import.

Weakness: CWE-1393 (Use of Default Password)

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


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

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

## Is CVE-2026-19851 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19851 is a high-severity vulnerability in Dassault Systèmes Tuleap Enterprise Edition, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19851 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-19851/ (Markdown: https://insights.sbomify.com/CVE-2026-19851/index.md)
```

## Sources

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

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