# CVE-2026-78158: Open5GS AMF UEContextReleaseRequest Path improper authorization

> Remote attackers can bypass authorization checks in the Open5GS AMF UEContextReleaseRequest handler, potentially disrupting 5G network operations.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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:** 24 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-87xw-rrcr-f94r, GHSA-mg8r-2cvv-xq9j

## What is CVE-2026-78158?

CVE-2026-78158 is a medium-severity missing authorization vulnerability in Open5GS, published on 24 Aug 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 Open5GS 2.8.0. This vulnerability affects unknown code of the component AMF UEContextReleaseRequest Path Handler. Executing a manipulation can lead to improper authorization. It is possible to launch the attack remotely.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-78158 being exploited?

There is no known exploitation of CVE-2026-78158 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78158 is a medium-severity missing authorization vulnerability in Open5GS, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78158 in the wild and no public exploit code.

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

## Sources

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

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