CVE-2025-29646

CVE-2025-29646 is a high-severity vulnerability in Open5gs with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-20.

Key facts

Description

An issue in upf in open5gs 2.7.2 and earlier allows a remote attacker to cause a Denial of Service via a crafted PFCP SessionEstablishmentRequest packet with restoration indication = true and (teid = 0 or teid >= ogs_pfcp_pdr_teid_pool.size).

Frequently asked questions

What is CVE-2025-29646?
An issue in upf in open5gs 2.7.2 and earlier allows a remote attacker to cause a Denial of Service via a crafted PFCP SessionEstablishmentRequest packet with restoration indication = true and (teid = 0 or teid >= ogs_pfcp_pdr_teid_pool.size).
How severe is CVE-2025-29646?
CVE-2025-29646 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity low, and availability none.
Is CVE-2025-29646 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-29646?
CVE-2025-29646 affects Open5gs. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-29646?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-29646 have an EU (EUVD) identifier?
Yes. CVE-2025-29646 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-18660.
When was CVE-2025-29646 published?
CVE-2025-29646 was published on 2025-06-18 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Open5gs

All CVEs affecting Open5gs →

Other CWE-20 (Improper Input Validation) vulnerabilities

Browse all CWE-20 (Improper Input Validation) vulnerabilities →