# CVE-2026-125390: Group-Office before 6.8.181, 25.0.116, and 26.0.58 Local File Read via processUploadQueue


- **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:** 9 Nov 2026
- **Also known as:** GHSA-7hj3-vffx-jm3w, GHSA-pf66-g36v-7698

## What is CVE-2026-125390?

CVE-2026-125390 is a high-severity vulnerability in Intermesh Group-Office, published on 9 Nov 2026. 

### Official description

Group-Office before 6.8.181, 25.0.116, and 26.0.58 contains an arbitrary local file read vulnerability in FolderController::actionProcessUploadQueue that allows authenticated users to read server files by supplying absolute paths in the blobs parameter. Attackers can have files hard-linked or copied into their own folder and downloaded, exposing other users' stored files and config.php database credentials.

Weakness: CWE-36 (Absolute Path Traversal)

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


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

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

## Is CVE-2026-125390 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: Intermesh Group-Office. 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-125390/ (Markdown: https://insights.sbomify.com/CVE-2026-125390/index.md)
```

## Sources

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

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