OpENer 2.3.0 CIP Message Parsing path_size out-of-bounds

Summaryinfo

A vulnerability was found in OpENer 2.3.0. It has been classified as problematic. The impacted element is an unknown function of the component CIP Message Parsing. This manipulation of the argument path_size causes out-of-bounds. This vulnerability is tracked as CVE-2026-51541. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in OpENer 2.3.0. It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component CIP Message Parsing. The manipulation of the argument path_size with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-51541 since 06/08/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/14/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• OpENer

Version

• 2.3.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion