# CVE-2026-91197: Flowable flowable-engine through 8.0.0 XXE via ProcessDiagramLayoutFactory


- **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:** 14 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-8x6x-vw5h-q563

## What is CVE-2026-91197?

CVE-2026-91197 is a high-severity vulnerability in flowable-engine, published on 14 Sep 2026. 

### Official description

Flowable flowable-engine through 8.0.0 contains an XML external entity injection vulnerability in ProcessDiagramLayoutFactory.parseXml() that fails to disable external entity resolution when parsing deployed BPMN resources. Attackers with process deployment privileges can embed DOCTYPE declarations with external entities in BPMN files to read arbitrary local files or trigger requests to internal network endpoints when diagram layout is computed.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


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

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

## Is CVE-2026-91197 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91197 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91197 is a high-severity vulnerability in flowable-engine, published on 14 Sep 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91197 exists.

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

## Sources

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

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