# CVE-2026-10114: Open5GS Shared NF-profile nnrf-handler.c handle_scp_info out-of-bounds write

> Remote attackers can trigger an out-of-bounds write in Open5GS via the Shared NF-profile Parser, 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:** No
- **Published:** 30 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-2vp2-c9x2-m79c

## What is CVE-2026-10114?

CVE-2026-10114 is a medium-severity memory corruption vulnerability in Open5GS, published on 30 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Open5GS up to 2.7.7. Affected by this issue is the function handle_scp_info in the library lib/sbi/nnrf-handler.c of the component Shared NF-profile Parser. This manipulation causes out-of-bounds write. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. To fix this issue, it is recommended to deploy a patch.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-10114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10114 is a medium-severity memory corruption vulnerability in Open5GS, published on 30 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-10114 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-10114/ (Markdown: https://insights.sbomify.com/CVE-2026-10114/index.md)
```

## Sources

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

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