# CVE-2026-92416: Open5GS PFCP Session Report Request n4-handler.c smf_n4_handle_session_report_request assertion

> Remote attackers can trigger a reachable assertion in Open5GS PFCP handler, causing a 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:X`)
- **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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-h3cw-r349-w992

## What is CVE-2026-92416?

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

### Official description

A vulnerability has been found in Open5GS up to 2.8.0. Affected by this issue is the function smf_n4_handle_session_report_request of the file src/smf/n4-handler.c of the component PFCP Session Report Request Handler. The manipulation leads to reachable assertion. The attack may be initiated remotely. The identifier of the patch is e5f0c06d0f2d9613b003daa1cfa3ba8a4bd157e9. It is suggested to install a patch to address this issue.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-92416 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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