Skip to main content
Menu
CVEs

free5GC SMF memory leak in SM context handling during PDU setup

CVE-2026-133700Published , updated

2.3LowCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

free5GC SMF leaves session contexts unreleased when retrieving a UDM access token fails during PDU session setup. A remote attacker with low-privilege access over the network can repeat these attempts while the NRF is unreachable, causing SMF memory use to keep growing.

Written by a model

Original description

free5GC SMF through 1.4.6 contains a resource leak vulnerability in HandlePDUSessionSMContextCreate that leaves SM contexts unreleased when UDM access token retrieval fails. Attackers can trigger repeated PDU session establishment attempts while the NRF is unreachable, causing empty 200 responses and persistent SMF memory growth.

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-133700 (free5GC SMF through 1.4.6 SM Context Leak via HandlePDUSessionSMContextCreate), 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-133700 (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-133700 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133700 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/244
- https://github.com/free5gc/free5gc/issues/1176
- https://github.com/free5gc/smf/blob/v1.4.6/internal/sbi/processor/pdu_session.go
- https://www.vulncheck.com/advisories/free5gc-smf-through-1.4.6-sm-context-leak-via-handlepdusessionsmcontextcreate
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-133700
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-133700"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • 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 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 6

Questions about CVE-2026-133700

Is CVE-2026-133700 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. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133700?

github.com/free5gc/smf (Go): through 1.4.6.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.