Security readout for executives and security teams
Plain-English summary
Open5GS versions 2.7.0 through 2.7.7 have a denial-of-service style issue in an NRF endpoint. A remote authenticated actor could cause resource consumption and reduce service availability. Sources say a patch is advised and the issue is already fixed, but they do not name a fixed release.
Executive priority
Treat as a near-term availability risk for environments that depend on Open5GS. Prioritize inventory and patch planning, especially for production 5G core testbeds or services where NRF instability could disrupt operations. Do not treat as confirmed ransomware-grade or actively exploited without more evidence.
Technical view
The flaw affects handle_amf_info in /lib/sbi/nnrf-handler.c for the nf-instances endpoint. Manipulation of nf_info_pool can lead to resource consumption, mapped to CWE-400 and CWE-404. CVSS v4.0 is 5.3 with network reachability, low complexity, privileges required, no user interaction, and low vulnerable-system availability impact.
Likely exposure
Exposure is likely where Open5GS 2.7.0 through 2.7.7 is deployed and the NRF nf-instances endpoint is reachable by authenticated or privileged network-function clients. The source bundle does not indicate impact to other products or unauthenticated internet-facing services.
Exploitation context
Public disclosure and exploit availability are reported by the source bundle, but CISA KEV is false and no cited source confirms active exploitation. The CVSS vector indicates remote exploitation with low complexity, but privileges are required and the expected impact is availability degradation rather than data theft or code execution.
Researcher notes
Evidence is limited to the CVE/VulDB description and linked Open5GS issue metadata in the bundle. The fixed status is stated, but the bundle does not provide a fixed version, commit, reproduction details suitable for validation, or proof of active exploitation. Avoid assuming broader Open5GS components are affected.
Mitigation direction
- Identify all Open5GS deployments and versions in mobile core environments.
- Apply the Open5GS fix or upgrade once the vendor identifies the fixed release.
- Restrict NRF endpoint access to trusted network-function components only.
- Monitor Open5GS NRF resource usage until patched.
- Review the linked Open5GS issue for project-specific fix guidance.
Validation and detection
- Confirm no production Open5GS instance runs versions 2.7.0 through 2.7.7.
- Verify the deployed build includes the upstream fix for issue 4480.
- Check NRF logs and metrics for unusual resource consumption patterns.
- Validate network controls limit access to the nf-instances endpoint.
- Document residual exposure where patch timing depends on vendor guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-404: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-10156 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (4.0)
- Known Exploited
- No
- Published
Vector: 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:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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:P——VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C2.81.4VulDBCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C2.81.4VulDBAV:N/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:OF/RC:C82.9VulDBVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: 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:P
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C
Base CVSS 3.0 score
4.3MediumVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C
Base CVSS 2.0 score
4MediumVector: AV:N/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:OF/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- VDB-367409 | Open5GS nf-instances Endpoint nnrf-handler.c handle_amf_info resource consumptionCVE reference, VulDB · vdb-entry, technical-description
- VDB-367409 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference, VulDB · signature, permissions-required
- Submit #818598 | Open5GS NRF v2.7.7 Denial of ServiceCVE reference, VulDB · third-party-advisory
- https://github.com/open5gs/open5gs/issues/4480CVE reference, VulDB · exploit, issue-tracking
- https://github.com/open5gs/open5gs/CVE reference, VulDB · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Resource Shutdown or Release
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.