CVE-2026-133700 json
free5GC SMF through 1.4.6 SM Context Leak via HandlePDUSessionSMContextCreate
published yesterday modified yesterday also EUVD-2026-131546
- cvss
- 2.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/free5gc/smf#244 pull request
Is CVE-2026-133700 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected products
- free5gc smf
Classification
- Weakness
-
- CWE-772 Missing Release of Resource after Effective Lifetime
References
-
github.com
/free5gc/smf/pull/244
issue-tracking, patch
-
github.com
/free5gc/free5gc/issues/1176
issue-tracking
-
github.com
/free5gc/smf/blob/v1.4.6/internal/sbi/processor/pdu_session.go
technical-description
-
vulncheck.com
/advisories/free5gc-smf-through-1.4.6-sm-context-leak-via-handlepdusessionsmcontextcreate
third-party-advisory
Sources
- CVE List CVE-2026-133700
- NVD CVE-2026-133700
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.