CVE-2026-133702 json
free5GC PCF through 1.4.6 Orphaned PCC Rules via Rejected Application Session Creation
published yesterday modified yesterday also EUVD-2026-131544
- cvss
- 5.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
free5GC PCF through 1.4.6 contains a resource leak in postAppSessCtxProcedure that leaves PCC rules and QoS data in the SM policy decision after rejected Npcf_PolicyAuthorization create requests. Authenticated AFs knowing an active PDU session's UE address can send repeated failing requests with distinct AF application identifiers to grow PCF memory and pollute policy sent to the SMF.
Patch / fix
Is CVE-2026-133702 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 FencerExploit prediction
0.42% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
Affected products
- free5gc pcf
Classification
- Weakness
-
- CWE-459 Incomplete Cleanup
References
-
github.com
/free5gc/pcf/commit/52c33ddff8e9a946c03b27c5d9b7a31c03030ca6
patch
-
github.com
/free5gc/free5gc/issues/1181
issue-tracking
-
github.com
/free5gc/free5gc/issues/1184
issue-tracking
-
github.com
/free5gc/pcf/blob/v1.4.6/internal/sbi/processor/policyauthorization.go#L163-L385
technical-description
-
vulncheck.com
/advisories/free5gc-pcf-through-1.4.6-orphaned-pcc-rules-via-rejected-application-session-creation
third-party-advisory
Sources
- CVE List CVE-2026-133702
- NVD CVE-2026-133702
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.