# CVE-2026-82589: Open5GS N1-N2 Message namf-handler.c amf_namf_comm_handle_n1_n2_message_transfer denial of service


- **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
- **Fix available:** No
- **Published:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-fgf3-pjr9-qfrf

## What is CVE-2026-82589?

CVE-2026-82589 is a medium-severity vulnerability in Open5GS, published on 30 Aug 2026. 

### Official description

A security flaw has been discovered in Open5GS up to 2.7.7. Impacted is the function amf_namf_comm_handle_n1_n2_message_transfer of the file src/amf/namf-handler.c of the component N1-N2 Message Handler. Performing a manipulation of the argument N1N2MessageTransferReqData.n2InfoContainer.smInfo.n2InfoContent.ngapIeType results in denial of service. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 2.8.0 is recommended to address this issue. The patch is named abf8a836564b966b5141110fc25ed413c4f17522. It is advisable to upgrade the affected component.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-82589 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82589 is a medium-severity vulnerability in Open5GS, published on 30 Aug 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82589 exists.

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

## Sources

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

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