CVE-2025-15419 — Open5GS GTPv2-C Flow s5c-handler.c sgwc_s5c_handle_create_session_response denial of service
A weakness has been identified in Open5GS up to 2.7.6. Affected by this issue is the function sgwc_s5c_handle_create_session_response of the file src/sgwc/s5c-handler.c of the component GTPv2-C Flow Handler. Executing a manipulation can lead to denial of service. The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. This patch is called 5aaa09907e7b9e0a326265a5f08d56f54280b5f2. It is advisable to implement a patch to correct this issue.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Open5gs Open5gs).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.8 | CVSS 4.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 1.9 | CVSS 4.0 | Low | — | — | cna@vuldb.com via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 3.3 | CVSS 3.1 | Low | 1.8 | 1.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 3.3 | CVSS 3.1 | Low | — | — | GitHub, Inc. via GitHub Security Advisories |
| 3.3 | CVSS 3.1 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 3.3 | CVSS 3.0 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 1.7 | CVSS 2.0 | Low | 3.1 | 2.9 | cna@vuldb.com via NIST National Vulnerability Database |
| 1.7 | CVSS 2.0 | Low | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.23%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Track CPU/memory spikes and availability drops correlated with request patterns.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
11 on the record
- github.com/open5gs/open5gs/issues/4224
- github.com/open5gs/open5gs/issues/4224
- github.com/open5gs/open5gs/issues/4224
- github.com/open5gs/open5gs/commit/5aaa09907e7b9e0a326265a5f08d56f54280b5f2
- github.com/advisories/GHSA-fprw-935f-f6f7
- github.com/open5gs/open5gs
- vuldb.com/
- vuldb.com/
- github.com/open5gs/open5gs/
- nvd.nist.gov/vuln/detail/CVE-2025-15419
- vuldb.com/
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-108103 Open5GS through 2.8.0 Heap Out-of-Bounds Read via PFCP Dropped DL Traffic Threshold IE 6d
- Medium CVE-2026-108105 Open5GS through 2.8.0 MME Reachable Assertion via GTPv1 SGSN Context Request 6d
- Medium CVE-2026-108102 Open5GS through 2.8.0 Heap Out-of-Bounds Read via PFCP Volume Measurement IE 6d
- High CVE-2026-15720 Pre-auth heap out-of-bounds read in the AMF NAS 5GS mobile-identity handler Jul 14, 2026
- Medium CVE-2026-8746 Open5GS NRF nghttp2-server.c discover_handler use after free May 17, 2026
- Medium CVE-2026-8745 Open5GS AUSF nausf-handler.c ogs_timer_add denial of service May 17, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-15419 is "Open5GS GTPv2-C Flow s5c-handler.c sgwc_s5c_handle_create_session_response denial of service", rated Medium. It affects Open5gs (Open5gs); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.