# CVE-2026-10703: EIPStackGroup OpENer SendRRData cipmessagerouter.c CreateMessageRouterRequestStructure use after free

> Remote attackers can exploit a use-after-free flaw in OpENer's SendRRData handler to potentially execute code or cause denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** AZL-89321, GHSA-vm9p-5mrq-6w5f

## What is CVE-2026-10703?

CVE-2026-10703 is a medium-severity use after free vulnerability in EIPStackGroup OpENer, published on 3 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in EIPStackGroup OpENer up to 2.3.0. Affected is the function CreateMessageRouterRequestStructure of the file cipmessagerouter.c of the component SendRRData Handler. The manipulation leads to use after free. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-10703?


## How do I fix CVE-2026-10703?

No fix has been published for CVE-2026-10703 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10703 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10703 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10703 and fix it if it is affected.

What it is: CVE-2026-10703 is a medium-severity use after free vulnerability in EIPStackGroup OpENer, published on 3 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10703 exists.

Affected product: EIPStackGroup OpENer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10703/ (Markdown: https://insights.sbomify.com/CVE-2026-10703/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10703
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10703
- OSV: https://osv.dev/vulnerability/CVE-2026-10703

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10703/
Summaries are generated and may contain mistakes; the official description above is the record.