Skip to main content
VulnerabilityPublished Updated

CVE-2026-1738: Open5GS · Reachable Assertion

Affects Open5GSSource CVE Database V5

0

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Open5GSAffected
  • 2.7.0 – 2.7.6
7 affected builds
Fixed in–
GitHubopen5gs/open5gspkg:github/open5gs/open5gsOther threatsAffected
  • 2.7.0 – 2.7.6
7 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:open5gs:open5gs:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-1738, organizations should immediately upgrade Open5GS to a version later than 2.7.6 where the vulnerability is fixed. If upgrading is not immediately feasible, applying any available patches or backported fixes from the Open5GS maintainers is critical. Network operators should implement strict network segmentation and firewall rules to restrict access to the SGWC interfaces, limiting exposure to untrusted networks. Monitoring and alerting for abnormal SGWC process crashes or assertion failures can help detect exploitation attempts early. Employing intrusion detection systems (IDS) with signatures for known exploit patterns can provide additional defense. Regularly auditing and updating 5G core network components and dependencies reduces exposure to known vulnerabilities. Finally, maintaining an incident response plan tailored to 5G infrastructure disruptions will help minimize downtime and impact if exploitation occurs.

Description

A flaw has been found in Open5GS up to 2.7.6. The impacted element is the function sgwc_tunnel_add of the file /src/sgwc/context.c of the component SGWC. Executing a manipulation of the argument pdr can lead to reachable assertion. The attack can be executed remotely. The exploit has been published and may be used. It is advisable to implement a patch to correct this issue. The issue report is flagged as already-fixed.

References

Community reviews

Loading reviews…