Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach UPF on PFCP UDP port 8805
-
ExploitSend Session Establishment/Modification request with DLPA+DLBY flags and short IE
-
ImpactTrigger heap out-of-bounds read crashing UPF
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target must be an Open5GS UPF (version 2.8.0 or earlier) reachable on UDP port 8805, and the attacker must be able to send PFCP Session Establishment or Modification Requests to it. The malicious packet must carry a Dropped DL Traffic Threshold IE with the DLPA and DLBY flags set but an IE length shorter than the flagged fields require, so the parser reads past the buffer. No authentication is required (PR:N) and no user interaction (UI:N). The key limiting factor is network position: the PFCP N4 interface is an internal core-network link between SMF and UPF and is not typically exposed to the internet, so exploitation realistically requires access to the operator's core signaling segment. |
| Impact | This is a medium-severity denial-of-service issue rather than a top-tier priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, unauthenticated, low-complexity reachability, but the only impact metric set is VA:L - no confidentiality (VC:N) or integrity (VI:N) impact - so despite being classified as an out-of-bounds read (CWE-125), the realistic outcome is a UPF crash, not data theft, consistent with the description's 'potentially crashing the UPF.' No EPSS score, KEV listing, or public exploit code is present in the provided data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The strongest mitigating real-world factor is deployment context: PFCP (the N4 interface, UDP 8805) runs between the SMF and UPF inside the mobile core and is not normally internet-exposed, so the nominal AV:N network vector is in practice reachable only by an attacker already positioned on the core signaling network. Net: a genuine but bounded availability risk - patch on a normal cycle and verify N4 segmentation; it is not a drop-everything emergency. |
| Exploit ScenarioDerived | An attacker with access to the mobile core's N4 signaling segment sends a crafted PFCP Session Establishment or Modification Request to the UPF on UDP port 8805 with the DLPA and DLBY flags set but a truncated Dropped DL Traffic Threshold IE. The parser ogs_pfcp_parse_dropped_dl_traffic_threshold() reads past the short IE buffer (heap out-of-bounds read), crashing the UPF and interrupting user-plane traffic. No public exploit code was identified in the provided data, though the VulnCheck advisory and the fix commit document the exact flaw. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
A heap out-of-bounds read in Open5GS 2.8.0 and earlier (ogs_pfcp_parse_dropped_dl_traffic_threshold() in lib/pfcp/types.c) lets remote unauthenticated attackers send malformed PFCP Session Establishment or Modification Requests to the UPF on UDP port 8805, using a Dropped DL Traffic Threshold IE with the DLPA and DLBY flags set but a too-short IE length, causing the parser to read past the end of the IE buffer and potentially crash the UPF. The assessed impact is availability-only (CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L; vendor score 6.9 under CVSS 4.0), so this is a medium-severity denial-of-service issue rather than a top-tier priority. No public exploit code has been identified at time of analysis and the CVE is not in CISA KEV, though the practical risk depends on exposure of the internal N4 interface.
RemediationAI
Upstream fix available (commit/PR); released patched version not independently confirmed in the available data, although the vendor advisory states a patch is available. The specific fix is commit 88e64fc1f87e0d321364b3bb710ef6a8f274e568 (https://github.com/open5gs/open5gs/commit/88e64fc1f87e0d321364b3bb710ef6a8f274e568), which introduces size-versus-IE-length bounds checks in ogs_pfcp_parse_dropped_dl_traffic_threshold() and related PFCP decoders; operators should either build from that commit or from the first upstream release that contains it once published. Because the N4/PFCP interface is an internal control-plane link between SMF and UPF that is not designed to be internet-exposed, the most effective compensating control is to restrict UDP 8805 to the specific SMF/peer addresses via host firewall or security-group rules and to ensure the UPF is never reachable from untrusted networks - the trade-off is that any legitimate SMF re-addressing or multi-SMF topology requires rule updates, and overly broad rules or NAT/proxy paths that mangle source addresses can break the rules or the association. Network detection should focus on anomalous PFCP Session Establishment/Modification messages carrying Dropped DL Traffic Threshold IEs with DLPA/DLBY flags and truncated lengths, and on UPF crash or restart events; because this is only an availability issue with no public exploit code identified at time of analysis, monitoring is a supplement to patching rather than a substitute for it.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Open5GS is an open-source implementation of the 5G core and EPC, and the affected component is its UPF (User Plane Function), which communicates with the SMF over the PFCP (Packet Forwarding Control Protocol) N4 interface on UDP port 8805. PFCP messages are composed of Information Elements encoded as TLV structures whose length field is attacker-controlled, so a parser must validate each field it reads against the declared IE length. The Dropped DL Traffic Threshold IE uses flag bits DLPA (downlink packets) and DLBY (downlink bytes) to signal which threshold fields follow; ogs_pfcp_parse_dropped_dl_traffic_threshold() trusted those flags and dereferenced the threshold, downlink_packets, and number_of_bytes_of_downlink_data fields without first confirming they fit inside the IE, producing a heap out-of-bounds read (CWE-125). The upstream fix (commit 88e64fc1f87e0d321364b3bb710ef6a8f274e568) adds explicit size-plus-field-length checks against octet->len and returns 0 on failure, and applies the same defensive pattern to several sibling PFCP parsers (sdf_filter, volume, volume_measurement) that shared the missing-bounds-check pattern, which points to a systemic TLV length-validation weakness in the PFCP decode path rather than a single isolated bug.
Know when Open5gs gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Remote, unauthenticated, low-complexity PFCP request (AV:N/AC:L/PR:N/UI:N); out-of-bounds read only crashes the UPF, so C:N/I:N and A:L.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Open5GS through 2.8.0 contains a heap out-of-bounds read vulnerability in ogs_pfcp_parse_dropped_dl_traffic_threshold() that allows remote unauthenticated attackers to read past IE buffers via short IEs. Attackers can send PFCP Session Establishment or Modification Requests to the UPF on UDP port 8805 with DLPA and DLBY flags set, potentially crashing the UPF.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
open5gs v2.6.4 is vulnerable to Buffer Overflow. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
Open5GS v2.6.4 is vulnerable to Buffer Overflow. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
A request-validation issue was discovered in Open5GS 2.1.3 through 2.2.x before 2.2.1. Rated critical severity (CVSS 9.8
Memory corruption in Open5GS versions through 2.7.1 is remotely exploitable via the freeDiameter protocol component, all
Open5GS 2.1.3 listens on 0.0.0.0:3000 and has a default password of 1423 for the admin account. Rated high severity (CVS
Open5GS MME versions <= 2.6.4 contain a reachable assertion in the `Uplink NAS Transport` packet handler. Rated high sev
Open5GS MME version <= 2.6.4 contains an assertion that can be remotely triggered via a malformed ASN.1 packet over the
Open5GS MME versions <= 2.6.4 contain an assertion that can be remotely triggered via a malformed ASN.1 packet over the
Open5GS MME versions <= 2.6.4 contains an assertion that can be remotely triggered via a malformed ASN.1 packet over the
EUVD-2026-95794
GHSA-4rxj-63ch-hjqf
NVD
CVE.org
EPSS
Exploit-DB