# CVE-2026-14618: Open5GS AMF nnrf-handler.c amf_nnrf_handle_nf_discover denial of service

> Remote attackers can cause a denial of service in Open5GS AMF via the nnrf-handler, requiring a patch to mitigate.

- **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:** No
- **Published:** 4 Jul 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-8r39-w67j-g66v

## What is CVE-2026-14618?

CVE-2026-14618 is a medium-severity denial of service vulnerability in Open5GS, published on 4 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in Open5GS up to 2.7.7. Affected by this vulnerability is the function amf_nnrf_handle_nf_discover of the file src/amf/nnrf-handler.c of the component AMF. The manipulation results in denial of service. The attack may be launched remotely. The exploit is now public and may be used. The patch is identified as fb5f67703de0213fb9c6e6ef3b48b6c1707e9503. It is best practice to apply a patch to resolve this issue.

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

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


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

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

## Is CVE-2026-14618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14618 is a medium-severity denial of service vulnerability in Open5GS, published on 4 Jul 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-14618 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-14618/ (Markdown: https://insights.sbomify.com/CVE-2026-14618/index.md)
```

## Sources

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

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