Security readout for executives and security teams
Plain-English summary
CVE-2025-56568 can let an unauthenticated remote attacker crash an Open5GS 5G core component by sending malformed network signaling data. The business impact is service disruption, not data theft. Organizations running Open5GS SMF before v2.7.5 should treat this as urgent availability risk.
Executive priority
Prioritize remediation for production Open5GS 5G core environments because the issue can disrupt service availability without authentication. It is less urgent for lab-only systems isolated from untrusted signaling sources.
Technical view
The flaw is an assertion failure in Open5GS SMF’s Protocol Configuration Options parser. Specially crafted NGAP messages with malformed length fields in protocol configuration data can trigger denial of service. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges or user interaction, availability impact only.
Likely exposure
Exposure is most relevant where Open5GS SMF is deployed and reachable by components or networks that can deliver NGAP signaling. Public internet exposure is not established by the sources. Affected versions are described as Open5GS before v2.7.5.
Exploitation context
No CISA KEV listing is provided, and the supplied sources do not claim active exploitation. The issue appears remotely triggerable and unauthenticated based on the CVE description, making untrusted or weakly segmented signaling paths the primary concern.
Researcher notes
Public details identify CWE-617 and a parser assertion failure involving malformed PCO length fields in NGAP messages. Avoid assuming broader Open5GS component impact beyond SMF. The supplied references include an issue and fixing commit, but no cited evidence of exploitation in the wild.
Mitigation direction
- Upgrade Open5GS to v2.7.5 or later where applicable.
- Review the linked Open5GS issue and commit for vendor-specific fix details.
- Restrict access to NGAP signaling paths to trusted network components.
- Monitor SMF process stability and unexpected restarts.
- If upgrade timing is unclear, check Open5GS guidance before applying workarounds.
Validation and detection
- Inventory Open5GS deployments and identify SMF instances.
- Confirm whether each deployment runs a version before v2.7.5.
- Review SMF logs for assertion failures or crashes around malformed PCO parsing.
- Verify NGAP signaling exposure is limited to trusted peers.
- Confirm the referenced fix is present after upgrade.
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-617: 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-2025-56568 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/open5gs/open5gs/issues/3969CVE reference, mitre
- https://github.com/open5gs/open5gs/commit/d7707879c943d2c952235382154d835b5849d54eCVE reference, mitre
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.
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.