# CVE-2026-106805: Free5GC SMF resource exhaustion in PFCP session establishment

Source: https://junglewise.ai/threats/cve-2026-106805-a-resource-exhaustion-issue-exists-in-free5gc-v4-2-3-during-pfcp  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2026-106805 · Severity: info · Published 2026-11-02

Free5GC is a 5G core network implementation used in mobile networks to manage user data sessions. A flaw in its Session Management Function (SMF) component fails to release IP address resources when PFCP signaling between the SMF and data plane (UPF) fails, allowing an attacker to exhaust the available IP pool and prevent new devices from connecting, causing network-wide denial of service.

Technologies: [free5GC](https://junglewise.ai/threats/technologies/free5gc). Vendors: [free5GC](https://junglewise.ai/threats/vendors/free5gc).

## Quick answers

**Is CVE-2026-106805 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-106805 being exploited in the wild.

**How severe is CVE-2026-106805?** Informational severity, published 2 November 2026.

**Which products and versions are affected?** free5GC v4.2.3.

**Is there a fix for CVE-2026-106805?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-106805 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-106805?** Check whether you run free5GC at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The SMF in Free5GC v4.2.3 does not properly release allocated UE IP addresses when a PFCP Session Establishment Response is not received from the UPF, even after retransmission timeouts. An attacker with network access to intercept or drop PFCP responses over the N4 interface can trigger repeated failed session establishments that accumulate unreleased IP resources. The vulnerability was fixed in the PFCP refactor that ensures SM context (including UE IP addresses) is released on the rejection path.

## Affected products

- Free5GC Free5GC v4.2.3

## Timeline

- 2026-09-10: disclosed
- 2026-11-02: advisory

## References

- [https://gist.github.com/hackeryounow/484987c16806c76dd53a8a87355dd0c2](https://gist.github.com/hackeryounow/484987c16806c76dd53a8a87355dd0c2)
- [https://github.com/free5gc/free5gc/issues/1162](https://github.com/free5gc/free5gc/issues/1162)

## Related threats

- [Free5GC race condition in GMM handler RanUe context access](https://junglewise.ai/threats/cve-2026-94043-a-vulnerability-was-determined-in-free5gc-up-to-4-2-3-this)
- [Free5GC UPF nil pointer dereference in PFCP Session Report](https://junglewise.ai/threats/cve-2026-75439-free5gc-upf-nil-pointer-dereference-in-pfcp-session-report)
- [free5GC NRF input validation bypass in NF profile registration](https://junglewise.ai/threats/cve-2026-55068-free5gc-nrf-input-validation-bypass-in-nf-profile-registration)
- [free5gc NSSF nil pointer dereference in NssaiAvailabilitySubscriptionCreate](https://junglewise.ai/threats/cve-2026-30073-free5gc-nssf-nil-pointer-dereference-in)
- [free5gc RechargePut denial of service in input parsing](https://junglewise.ai/threats/cve-2026-30071-free5gc-rechargeput-denial-of-service-in-input-parsing)