free5GC SMF resource exhaustion in PDU session establishment
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
free5GC SMF contains a resource exhaustion flaw. An authenticated attacker with low privileges can reach it remotely over the network by repeatedly establishing PDU sessions during NRF or AMF failures, which leaks session contexts, UE IP addresses and TEIDs until the DNN IP pool is exhausted. No user action is needed.
Written by a model
Original description
free5GC SMF through 1.4.6 contains a resource exhaustion vulnerability because sendPDUSessionEstablishmentAccept returns early without calling RemoveSMContextFromAllNF on failures. Authenticated UEs repeatedly establishing PDU sessions during NRF or AMF failures leak SM contexts, UE IP addresses and TEIDs, exhausting the DNN IP pool.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133699 (free5GC SMF through 1.4.6 Resource Exhaustion via sendPDUSessionEstablishmentAccept), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133699 (entry last updated 2026-11-20):
Affected:
- Go package github.com/free5gc/smf: through 1.4.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133699 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133699 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/free5gc/smf/pull/246
- https://github.com/free5gc/smf/commit/0c1715f951c73d382b93b787a9fd4d5c96d59a99
- https://github.com/free5gc/free5gc/issues/1177
- https://github.com/free5gc/smf/blob/v1.4.6/internal/sbi/processor/datapath.go
- https://www.vulncheck.com/advisories/free5gc-smf-through-1.4.6-resource-exhaustion-via-sendpdusessionestablishmentaccept
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133699
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133699"}.Affected versions
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Go packages
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 49 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133699 |
| Record | NVD · CVE-2026-133699 |
| Other links 5 | |
| Patch | GitHub · free5gc/smf · Pull request #246 |
| Patch | GitHub · free5gc/smf · Commit 0c1715f9 |
| Report | GitHub · free5gc/free5gc · Issue #1177 |
| Repository | GitHub · free5gc/smf · internal/sbi/processor/datapath.go |
| Link | vulncheck.com · advisories/free5gc-smf-through-1.4.6-resource-exhaustion-via-sendpdusessionestablishmentaccept |
Questions about CVE-2026-133699
Is CVE-2026-133699 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133699?
github.com/free5gc/smf (Go): through 1.4.6.
Source: cve.now feed data
Related
- CVE-2026-44329free5GC: SMF UPI management interface lacks auth middleware; unauthenticated topology read/write requests reach handlers
- CVE-2026-44328free5GC: SMF UPI DELETE /upi/v1/upNodesLinks/{ref} panics on AN-node deletion via nil UPF dereference; unauthenticated, state-mutating
- CVE-2026-44321free5GC: SMF UPI POST /upi/v1/upNodesLinks exits the SMF process on overlapping UE pools (unauthenticated, reachable Fatalf)
- CVE-2026-133700free5GC SMF through 1.4.6 SM Context Leak via HandlePDUSessionSMContextCreate
- CVE-2026-133701free5GC SMF through 1.4.6 Resource Exhaustion via Orphaned SM Contexts
- CVE-2026-1684Free5GC SMF PFCP UDP Endpoint pfcp_reports.go HandleReports denial of service
No corrections so far. Something wrong on this page? Report an error.