# CVE-2026-51541: Memory corruption in n/a

> An attacker can trigger an out-of-bounds read in OpENer by sending malformed CIP requests, potentially causing crashes or leaking memory.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-6q7w-q386-7c4j

## What is CVE-2026-51541?

CVE-2026-51541 is a critical memory corruption vulnerability in n/a, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpENer 2.3.0 (commit 76b95cf) has an out-of-bounds read issue in CIP message parsing when handling malformed explicit requests with a forged EPath size. An attacker can send a valid ENIP SendRRData frame carrying a very short CIP payload whose path_size field claims that many more path words are present than are actually available. Because the parser trusts the attacker-controlled path_size and continues decoding path segments without a remaining-length boundary, it reads beyond the end of the stack receive buffer.

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

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

It affects 1 product.


Products: Opener Project Opener.

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

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

## Is CVE-2026-51541 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43604](https://insights.sbomify.com/CVE-2022-43604/): Memory corruption in OpENer (critical 10.0)
- [CVE-2022-43605](https://insights.sbomify.com/CVE-2022-43605/): Memory corruption in OpENer (critical 10.0)
- [CVE-2026-51540](https://insights.sbomify.com/CVE-2026-51540/): Integer overflow in n/a (critical 9.8)
- [CVE-2020-13556](https://insights.sbomify.com/CVE-2020-13556/): Memory corruption in EIP Stack Group (critical 9.8)
- [CVE-2026-51536](https://insights.sbomify.com/CVE-2026-51536/): Integer overflow in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51541 is a critical memory corruption vulnerability in n/a, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51541 exists.

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

## Sources

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

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