Vulnerability Description
In OpENer 2.3.0 (commit 76b95cf) when parsing incoming CIP (Common Industrial Protocol) network packets, the length parameter is inconsistently typed across the call stack. Specifically, an upstream length calculated as an int is passed to a downstream function that expects an EipInt16 (a 16-bit signed integer). If a maliciously crafted packet with specific length fields is processed, the length parameter can overflow or be truncated into a negative value. This negative length bypasses subsequent bounds checking (due to signed/unsigned comparison issues) and is ultimately used in memory operations, leading to a Stack Buffer Overflow when reading data in DecodePaddedEPath.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Opener Project | Opener | 2.3.0 |
Related Weaknesses (CWE)
References
- https://gist.github.com/MrAlaskan/e160c626a32e03e5d9eddaa732560672Third Party Advisory
- https://github.com/EIPStackGroup/OpENer/issues/563ExploitIssue TrackingVendor Advisory
- https://github.com/EIPStackGroup/OpENer/issues/563ExploitIssue TrackingVendor Advisory
FAQ
What is CVE-2026-51536?
CVE-2026-51536 is a vulnerability with a CVSS score of 9.1 (CRITICAL). In OpENer 2.3.0 (commit 76b95cf) when parsing incoming CIP (Common Industrial Protocol) network packets, the length parameter is inconsistently typed across the call stack. Specifically, an upstream l...
How severe is CVE-2026-51536?
CVE-2026-51536 has been rated CRITICAL with a CVSS base score of 9.1/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-51536?
Check the references section above for vendor advisories and patch information. Affected products include: Opener Project Opener.