# CVE-2026-76157: Datiphy Data Management Center - Missing Authentication for Critical Function

> Unauthenticated attackers can upload arbitrary files to the server, potentially leading to remote code execution or data modification.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/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:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-fgmq-h6gh-p5x7

## What is CVE-2026-76157?

CVE-2026-76157 is a high-severity missing authorization 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

Missing authentication for a critical function in the upload API endpoint of Datiphy Data Management Center from v8.3.0 through v8.5.1 allows an unauthenticated remote attacker to upload arbitrary files to the server's configured upload directory.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-76157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76157 is a high-severity missing authorization 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-76157 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-76157/ (Markdown: https://insights.sbomify.com/CVE-2026-76157/index.md)
```

## Sources

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

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