# CVE-2026-6071: Code Execution Vulnerability in Arena®

> Remote attackers can execute arbitrary code by tricking users into opening malicious DOE files in Rockwell Arena.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-gf3c-4ghw-6f87

## What is CVE-2026-6071?

CVE-2026-6071 is a high-severity memory corruption vulnerability in Rockwell Automation Arena, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A remote code execution security issue exists in the affected products when parsing DOE files that could allow a remote attacker to write past the end of an allocated object and execute code within the context of the current process. To exploit this vulnerability, a legitimate user must visit a malicious page or open a malicious file.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-6071 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6071 is a high-severity memory corruption vulnerability in Rockwell Automation Arena, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-6071 in the wild and no public exploit code.

Affected product: Rockwell Automation Arena. 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-6071/ (Markdown: https://insights.sbomify.com/CVE-2026-6071/index.md)
```

## Sources

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

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