CVE-2026-8122
Denial of Service in Open5GS NSSF Component
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| open5gs | open5gs | to 2.7.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-404 | The product does not release or incorrectly releases a resource before it is made available for re-use. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Open5GS up to version 2.7.7, specifically in the Network Slice Selection Function (NSSF) component. It occurs in the function ogs_sbi_discovery_option_add_service_names within the /lib/sbi/message.c library. When a GET request is made to the endpoint `/nnssf-nsselection/v2/network-slice-information` with an oversized `service-names` query parameter (exceeding the allowed number), the parser triggers an assertion failure. This causes the NSSF process to crash and terminate unexpectedly.
The root cause is that the parser does not properly handle requests with too many service names, leading to a denial of service through process termination instead of gracefully handling the error.
How can this vulnerability impact me? :
This vulnerability can cause a denial of service (DoS) by crashing the NSSF component of Open5GS when it receives a specially crafted request with too many service names. Since the NSSF process terminates unexpectedly, it can disrupt network slice selection services, potentially affecting the availability and reliability of the affected system.
Because the attack can be performed remotely by sending a malicious GET request, it poses a risk of service interruption without requiring local access.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for crashes or unexpected termination of the NSSF process in Open5GS when it processes specific HTTP GET requests.
Specifically, sending a GET request to the endpoint `/nnssf-nsselection/v2/network-slice-information` with an oversized `service-names` query parameter (e.g., 80 service names) can trigger the vulnerability and cause the NSSF to crash.
- Use a command like curl to send a crafted request: curl -v "http://<open5gs-nssf-ip>:<port>/nnssf-nsselection/v2/network-slice-information?service-names=name1,name2,...,name80"
- Monitor the NSSF process logs or system logs for exit code 139 or assertion failures indicating a crash.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or filtering incoming requests to the NSSF component to prevent oversized `service-names` query parameters.
Implement network-level protections such as firewall rules or API gateways to block or limit requests with excessive query parameters targeting the vulnerable endpoint.
Monitor the NSSF process for crashes and consider restarting it automatically if it terminates unexpectedly.
Since the project has not yet responded with a fix, stay updated on official patches or updates from Open5GS and apply them once available.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.