Skip to main content
CVE-2025-44951VulnerabilityPublished Updated

CVE-2025-44951: open5gs · n/a

Affects open5gsSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubopen5gs/open5gspkg:github/open5gs/open5gsOther threatsAffected
  • <=2.7.2
Fixed in–

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

AI-suggested

1. Monitor open5gs deployments and identify all instances running version 2.7.2 or earlier. 2. Apply official patches or updates from the open5gs project as soon as they become available. 3. Until patches are released, implement strict input validation on the session.dev field to enforce maximum length constraints at the application or network interface level. 4. Restrict local access to SMF and UPF hosts to trusted personnel only, employing strong authentication and access controls to minimize the risk of local exploitation. 5. Deploy host-based intrusion detection systems (HIDS) to detect anomalous behavior or memory corruption attempts on affected systems. 6. Conduct regular audits of user accounts and privileges on telecom infrastructure to prevent unauthorized local access. 7. Network segmentation should be enforced to isolate critical 5G core components from less trusted network zones. 8. Engage with open5gs community and security advisories to stay informed about patches and exploit developments. 9. Consider deploying runtime protections such as stack canaries, ASLR, and DEP on affected hosts to mitigate exploitation impact. 10. Prepare incident response plans specifically addressing potential 5G core network compromises.

Description

A missing length check in `ogs_pfcp_dev_add` function from PFCP library, used by both smf and upf in open5gs 2.7.2 and earlier, allows a local attacker to cause a Buffer Overflow by changing the `session.dev` field with a value with length greater than 32.

References

Community reviews

Loading reviews…