# CVE-2026-78674: Remote Code Execution via BPMN System REST APIs in Multiple WSO2 Products Permits Arbitrary Command Execution


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hqmm-q55h-r6p8

## What is CVE-2026-78674?

CVE-2026-78674 is a high-severity vulnerability in WSO2 Business Process Server, published on 28 Oct 2026. 

### Official description

The BPMN System REST APIs do not sufficiently validate input parameters, allowing authenticated users to submit crafted requests that can lead to the execution of arbitrary commands on the server.

An authenticated user can leverage this vulnerability to execute arbitrary commands with the privileges of the product's runtime account. The scope of potential damage is contingent upon the permissions assigned to this account.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-78674 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78674 is a high-severity vulnerability in WSO2 Business Process Server, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-78674 in the wild and no public exploit code.

Affected product: WSO2 Business Process Server. 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-78674/ (Markdown: https://insights.sbomify.com/CVE-2026-78674/index.md)
```

## Sources

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

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