CVE-2025-52288 json
Assertion failure in function ngap_build_downlink_nas_transport in file src/amf/ngap-build.c, the Access and Mobility Management Function (…
published 2025-09-08 14 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-27173
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Assertion failure in function ngap_build_downlink_nas_transport in file src/amf/ngap-build.c, the Access and Mobility Management Function (AMF) component, in Open5GS thru 2.7.5 allowing attackers to cause a denial of service or other unspecified impacts via repeated UE connect and disconnect message sequences.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 14 mo ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/open5gs/open5gs/issues/3862 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/open5gs/open5gs/issues/3862#issue-3006335547 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/matejGradisar/open5gs/commit/5467da9763c300520f56bfbe0a7f5a7f980ec2f6
patch
-
github.com
/open5gs/open5gs/issues/3862
exploit, issue-tracking
-
github.com
/open5gs/open5gs/issues/3862#issue-3006335547
exploit, issue-tracking
-
github.com
/open5gs/open5gs/issues/3862#issuecomment-2853458783
issue-tracking
-
github.com
/ZHENGHAOHELLO/BugReport/blob/main/CVE-2025-52288
third-party-advisory
Sources
- CVE List CVE-2025-52288
- NVD CVE-2025-52288
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.