CVE-2026-78158
Received Received - Intake

Improper Authorization in Open5GS AMF UEContextReleaseRequest Path Handler

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-24
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
CVE-2026-78158
EUVD
EUVD-2026-64676

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
open5gs open5gs to 2.8.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-266 A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Open5GS 2.8.0 involves the AMF UEContextReleaseRequest Path Handler. An attacker can remotely manipulate the system to improperly authorize actions, leading to unauthorized UE context release requests. The flaw allows sending a UEContextReleaseRequest from a different NG-RAN SCTP association than the one controlling the UE context, causing the AMF to incorrectly release the UE context.

Detection Guidance

Monitor AMF logs for unexpected UEContextReleaseRequest messages from unassociated NG-RAN nodes. Check for mismatched NGAP identifiers or SCTP associations triggering UE context releases. Use network traffic analysis tools like Wireshark to inspect NGAP protocol messages for irregular UEContextReleaseRequest patterns.

Impact Analysis

This vulnerability can lead to targeted availability loss for affected users. An attacker with access to the N2/NG-RAN network interface can force the release of a UE context belonging to another user, disrupting their network service. It does not allow code execution, data disclosure, or bypass of network access controls.

Compliance Impact

This vulnerability primarily impacts availability and integrity, not confidentiality. While it does not directly cause data breaches, it could disrupt services critical to compliance with availability requirements in standards like GDPR or HIPAA. Organizations must ensure network access controls are in place to mitigate such risks.

Mitigation Strategies

Update Open5GS to the latest commit or patch addressing this issue. Implement strict validation of NGAP identifiers and SCTP associations in AMF to ensure UEContextReleaseRequest messages originate from the correct NG-RAN node. Restrict network access to the N2/NG-RAN interface to trusted entities only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-78158. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart