# CVE-2026-8349: omec-project amf NGAP Message memory corruption

> Remote attackers can trigger memory corruption in the NGAP Message Handler of the omec-project AMF, potentially leading to code execution or service disruption.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/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:** Yes
- **Published:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-3h63-fx68-x5fm, GO-2026-5087

## What is CVE-2026-8349?

CVE-2026-8349 is a medium-severity memory corruption vulnerability in omec-project amf, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in omec-project amf up to 2.1.1. This vulnerability affects unknown code of the component NGAP Message Handler. Executing a manipulation can lead to memory corruption. The attack can be launched remotely. The exploit has been published and may be used. This patch is called 8a4c33cdda866094f1989bdeff6d8642fce8de8435f89defd66831c97715f5aa. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

3 open source packages ship an affected version, including github.com/omec-project/amf.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/omec-project/amf` | Go | All versions | None |
| `github.com/omec-project/amf` | Go | All versions to 1.7.0 | None |
| `github.com/omec-project/amf` | Go | All versions to 1.7.0 | None |

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

Apply the vendor's patch.

## Is CVE-2026-8349 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8349 is a medium-severity memory corruption vulnerability in omec-project amf, published on 11 May 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-8349 exists.

Affected packages and fixed versions:
- github.com/omec-project/amf (Go): affected all versions; no fix listed
- github.com/omec-project/amf (Go): affected all versions up to 1.7.0; no fix listed
- github.com/omec-project/amf (Go): affected all versions up to 1.7.0; no fix listed

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-8349/ (Markdown: https://insights.sbomify.com/CVE-2026-8349/index.md)
```

## Sources

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

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