Quick answers
- Is CVE-2026-10703 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10703 being exploited in the wild.
- How severe is CVE-2026-10703?
- Medium severity, with a CVSS score of 6.3, published 3 June 2026.
- Which products and versions are affected?
- EIPStackGroup OpENer up to 2.3.0.
- Is there a fix for CVE-2026-10703?
- 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-10703 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-10703?
- 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
A use-after-free (specifically a stack-use-after-return) vulnerability exists in the SendRRData Handler component of OpENer. The root cause is incorrect lifetime management of the CIP payload pointer across the TCP receive, encapsulation, and Common Packet Format (CPF) parsing layers. Specifically, HandleDataOnTcpSocket receives data into a stack-backed buffer, but the CPF layer stores a raw pointer to this buffer instead of copying the data. When CreateMessageRouterRequestStructure in cipmessagerouter.c later attempts to dereference this pointer after the original function has returned, it triggers a memory corruption event. An attacker can exploit this by sending a crafted EtherNet/IP explicit-message packet over TCP. As of the advisory date, the project has been notified but a formal patch has not been confirmed.
Affected products
- EIPStackGroup OpENer up to 2.3.0
Timeline
- 2026-06-03: advisory: Vulnerability disclosed via VulDB and NVD
- 2026-06-03: other: Public proof-of-concept exploit released