# CVE-2026-125380: DataRoom through 3.0.0 Incorrect Authorization via /dataRoom/dataset/run/test


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-mppv-m824-3w4x

## What is CVE-2026-125380?

CVE-2026-125380 is a high-severity vulnerability in gcpaas DataRoom, published on 9 Nov 2026. 

### Official description

DataRoom through 3.0.0 contains an incorrect authorization vulnerability in DatasetController.runTest that allows visitor-role users to execute dataset definitions supplied in the request body. Attackers can specify an arbitrary dataSourceCode and raw SELECT SQL to query any configured relational data source using its stored decrypted credentials, bypassing developer-only restrictions.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-125380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125380 is a high-severity vulnerability in gcpaas DataRoom, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125380 in the wild and no public exploit code.

Affected product: gcpaas DataRoom. 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-125380/ (Markdown: https://insights.sbomify.com/CVE-2026-125380/index.md)
```

## Sources

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

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