# CVE-2026-10157: Open5GS NGAP PathSwitchRequest Message ngap-handler.c improper authentication

> Remote attackers can bypass authentication in Open5GS AMF via NGAP PathSwitchRequest messages, requiring a patch to secure the network core.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-89hg-mhjp-f99q

## What is CVE-2026-10157?

CVE-2026-10157 is a medium-severity authentication bypass vulnerability in Open5GS, published on 31 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in Open5GS up to 2.7.6. This impacts an unknown function of the file src/amf/ngap-handler.c of the component NGAP PathSwitchRequest Message Handler. The manipulation leads to improper authentication. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The identifier of the patch is a188e36b1741ffc2252133f59b1bda4f14d3cb5c. It is suggested to install a patch to address this issue.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-10157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10157 is a medium-severity authentication bypass vulnerability in Open5GS, published on 31 May 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-10157 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-10157/ (Markdown: https://insights.sbomify.com/CVE-2026-10157/index.md)
```

## Sources

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

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