Quick answers
- Is CVE-2026-51541 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51541 being exploited in the wild.
- How severe is CVE-2026-51541?
- Informational severity, with a CVSS score of 7.5, published 13 July 2026.
- Which products and versions are affected?
- EIPStackGroup OpENer 2.3.0 (commit 76b95cf).
- Is there a fix for CVE-2026-51541?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-51541 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-51541?
- Check whether you run EIPStackGroup OpENer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read vulnerability exists in OpENer 2.3.0 (commit 76b95cf) within the CIP explicit message parsing logic. The issue resides in the `DecodePaddedEPath` function in `cipcommon.c` and `CreateMessageRouterRequestStructure` in `cipmessagerouter.c`. The parser trusts an attacker-controlled `path_size` field in a malformed ENIP SendRRData frame without verifying the actual remaining length of the input buffer. An unauthenticated remote attacker can provide a forged EPath size that exceeds the available data, causing the decoder to read beyond the 512-byte stack receive buffer. This leads to a stack-buffer-overflow (as detected by AddressSanitizer) and an immediate process crash (Denial of Service).
Affected products
- EIPStackGroup OpENer 2.3.0 (commit 76b95cf)
Timeline
- 2026-06-05: disclosed: Issue reported on GitHub by MrAlaskan
- 2026-07-09: advisory: Security advisory published by MrAlaskan
- 2026-07-13: advisory: CVE published to NVD dataset