CVE-2026-1974VulnerabilityPublished 6 Feb 2026Updated 23 Feb 2026

CVE-2026-1974: Free5GC · Denial of Service

Affects Free5GCSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Free5GC	Affected =4.0 =4.1.0	Fixed in–
Gogithub.com/free5gc/free5gc`pkg:golang/github.com/free5gc/free5gc`Other threats	Affected =4.0 =4.1.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:free5gc:free5gc:*:*:*:*:*:*:*:*

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

AI-suggested

To mitigate CVE-2026-1974, organizations should promptly apply the official patches or updates released by the Free5GC maintainers addressing the ResolveNodeIdToIp function vulnerability. In the absence of an immediate patch, network administrators should implement strict network segmentation and firewall rules to restrict access to the SMF interfaces, limiting exposure to untrusted networks. Deploying intrusion detection and prevention systems (IDS/IPS) with signatures tuned to detect anomalous or malformed requests targeting the SMF can help identify and block exploitation attempts. Regularly monitoring SMF logs and system health metrics can provide early warning signs of attempted or successful DoS attacks. Additionally, organizations should conduct thorough input validation and fuzz testing on their 5G core components to identify and remediate similar vulnerabilities proactively. Employing redundancy and failover mechanisms for the SMF can reduce the impact of potential service disruptions. Finally, maintaining an up-to-date asset inventory and vulnerability management program focused on 5G infrastructure components will ensure timely detection and response to emerging threats.

Description

A vulnerability was identified in Free5GC up to 4.1.0. This affects the function ResolveNodeIdToIp of the file internal/sbi/processor/datapath.go of the component SMF. The manipulation leads to denial of service. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. It is recommended to apply a patch to fix this issue.

Impact

The primary impact of CVE-2026-1974 is the disruption of 5G core network services due to denial of service in the SMF component. This can lead to session management failures, dropped connections, and degraded network performance, affecting end-user experience and potentially causing outages in 5G services. For telecom operators and enterprises relying on Free5GC for 5G core functions, this vulnerability could result in service downtime, loss of revenue, and damage to reputation. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially in environments where Free5GC is exposed to untrusted networks. Additionally, disruption in 5G core functions could impact critical services that depend on 5G connectivity, including IoT deployments, emergency communications, and industrial automation. While no known active exploitation is reported, the availability of a public exploit lowers the barrier for attackers to launch DoS attacks, potentially leading to targeted or opportunistic disruptions. Organizations worldwide deploying Free5GC or similar open-source 5G core solutions must consider the operational and security implications of this vulnerability.

References

Community reviews

Loading reviews…