CVE-2026-51536

Published Jul 13, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A stack buffer overflow occurs when OpENer 2.3.0 parses CIP packets because an upstream length field calculated as an int is passed to a downstream function that expects a 16-bit signed integer, allowing maliciously crafted packets to produce negative or truncated lengths. The negative length bypasses bounds checks due to signed/unsigned mismatches and is subsequently used in memory operations during DecodePaddedEPath, enabling an attacker to corrupt the stack and execute arbitrary code, which compromises confidentiality, integrity, and availability.

Affected Systems

Devices running OpENer 2.3.0 (commit 76b95cf) are vulnerable; earlier or patched releases are not affected.

Risk and Exploitability

The CVSS score of 9.1 signals a high‑severity vulnerability. The EPSS score is less than 1%, indicating a very low current probability of exploitation, yet the flaw remains a critical stack buffer overflow that can be triggered by network‑based crafted CIP packets. It is not listed in the CISA KEV catalog. An attacker with network access capable of transmitting such packets can potentially achieve remote code execution on the affected device.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a patched OpENer release that corrects the length handling in CIP packet parsing.
  • If an update is not yet available, isolate OpENer devices behind a firewall and restrict inbound CIP traffic to trusted hosts.
  • Disable or remove the use of CIP protocol if it is not required by the application.
  • Monitor system logs for DecodePaddedEPath failures or stack corruption messages and treat any such events as security incidents.

Generated by OpenCVE AI on July 31, 2026 at 12:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Opener Project
Opener Project opener
CPEs cpe:2.3:a:opener_project:opener:2.3.0:*:*:*:*:*:*:*
Vendors & Products Opener Project
Opener Project opener
Type Values Removed Values Added
Title Stack Buffer Overflow in OpENer 2.3.0 CIP Packet Parsing
Type Values Removed Values Added
Title Stack Buffer Overflow in OpENer 2.3.0 CIP Packet Parsing
Type Values Removed Values Added
Title Stack Buffer Overflow in OpENer 2.3.0 CIP Protocol Allows Remote Code Execution
Type Values Removed Values Added
Title Stack Buffer Overflow in OpENer 2.3.0 CIP Protocol Allows Remote Code Execution
Type Values Removed Values Added
Title Stack Buffer Overflow in OpENer 2.3.0 due to Signed/Unsigned Length Misuse in CIP Packet Parsing
Weaknesses CWE-129
CWE-194
Type Values Removed Values Added
Title Stack Buffer Overflow in OpENer 2.3.0 due to Signed/Unsigned Length Misuse in CIP Packet Parsing
Weaknesses CWE-129
CWE-194
Type Values Removed Values Added
Weaknesses CWE-190
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Eipstackgroup
Eipstackgroup opener
Vendors & Products Eipstackgroup
Eipstackgroup opener
Type Values Removed Values Added
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.
References
Weaknesses
  • CWE-190

    Integer Overflow or Wraparound

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Jul 14, 2026, 1:39 PM
Reserved
Jun 8, 2026, 12:00 AM
Status
Analyzed
Published
Jul 13, 2026, 10:16 PM
Modified
Aug 11, 2026, 4:43 PM