# CVE-2026-107188: Eptura Archibus Workflow Rule Enables Unauthenticated Arbitrary File Upload Leading to Remote Code Execution

> Unauthenticated attackers can upload malicious JSP files via export reports to execute arbitrary code on the server.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-pv68-m9mv-v63w

## What is CVE-2026-107188?

CVE-2026-107188 is a critical vulnerability in Eptura Archibus, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A user can upload export reports with any file contents and specify any contents. JSP code can be uploaded, JSPX can be specified as the file extension, and anyone can browse to the uploaded file, leading to command execution. The authentication bypass vulnerability can be chained with this vulnerability to run code on the server without authentication.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-107188 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107188 is a critical vulnerability in Eptura Archibus, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107188 in the wild and no public exploit code.

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

## Sources

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

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