# CVE-2026-51221: Memory corruption in n/a

> Attackers can cause a Denial of Service in EIPStackGroup OpENer by sending a crafted Common Packet Format packet that triggers a buffer overflow.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-p26f-vx3f-455g

## What is CVE-2026-51221?

CVE-2026-51221 is a high-severity memory corruption vulnerability in n/a, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow in the Get_Attribute_List function of EIPStackGroup OpENer commit 76b95c allows attackers to cause a Denial of Service (DoS) via supplying a crafted Common Packet Format (CPF) packet.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-51221 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51221 is a high-severity memory corruption vulnerability in n/a, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51221 exists.

Affected product: n/a. 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-51221/ (Markdown: https://insights.sbomify.com/CVE-2026-51221/index.md)
```

## Sources

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

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