# CVE-2025-0591: Out-of-bounds Read vulnerability in CX-Programmer

> Attackers can read sensitive information or crash the application via an out-of-bounds read in OMRON CX-Programmer.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-xv4j-6mfg-j9p6

## What is CVE-2025-0591?

CVE-2025-0591 is a high-severity vulnerability in OMRON Corporation FA Integrated Tool Package CX-One, published on 16 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Out-of-bounds Read vulnerability (CWE-125) was found in CX-Programmer. Attackers may be able to read sensitive information or cause an application crash by abusing this vulnerability.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-0591?


## How do I fix CVE-2025-0591?

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

## Is CVE-2025-0591 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0591 and fix it if it is affected.

What it is: CVE-2025-0591 is a high-severity vulnerability in OMRON Corporation FA Integrated Tool Package CX-One, published on 16 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0591 in the wild and no public exploit code.

Affected product: OMRON Corporation FA Integrated Tool Package CX-One. 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-2025-0591/ (Markdown: https://insights.sbomify.com/CVE-2025-0591/index.md)
```

## Sources

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

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