# CVE-2026-76158: Datiphy Data Management Center - External Control of File Name or Path

> Remote attackers can write files to arbitrary locations outside the intended upload directory via path traversal in the upload API.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-3g7v-7vpf-gwmm

## What is CVE-2026-76158?

CVE-2026-76158 is a critical path traversal vulnerability in Datiphy Inc. Data Management Center, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

External Control of File Name or Path in the upload API endpoint of Datiphy Data Management Center from v8.3.0 through v8.5.1 allows a remote attacker to write files to arbitrary locations outside the intended upload directory via relative or absolute path sequences.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-76158 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76158 is a critical path traversal vulnerability in Datiphy Inc. Data Management Center, published on 21 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-76158 in the wild and no public exploit code.

Affected product: Datiphy Inc. Data Management Center. 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-76158/ (Markdown: https://insights.sbomify.com/CVE-2026-76158/index.md)
```

## Sources

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

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