free5GC PCF resource leak in application session creation
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
free5GC PCF has a resource leak that lets a remote attacker with low-privilege login, specifically an authenticated AF that knows an active PDU session's UE address, leave orphaned policy rules and QoS data behind through repeated failing requests. Those requests can grow PCF memory use and pollute the policy sent to the SMF.
Written by a model
Original description
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.
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-133702 (free5GC PCF through 1.4.6 Orphaned PCC Rules via Rejected Application Session Creation), 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-133702 (entry last updated 2026-11-20):
Affected:
- Go package github.com/free5gc/pcf: 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-133702 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133702 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/pcf/commit/52c33ddff8e9a946c03b27c5d9b7a31c03030ca6
- https://github.com/free5gc/free5gc/issues/1181
- https://github.com/free5gc/free5gc/issues/1184
- https://github.com/free5gc/pcf/blob/v1.4.6/internal/sbi/processor/policyauthorization.go#L163-L385
- https://www.vulncheck.com/advisories/free5gc-pcf-through-1.4.6-orphaned-pcc-rules-via-rejected-application-session-creation
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-133702
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-133702"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Go packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133702 |
| Record | NVD · CVE-2026-133702 |
| Other links 5 | |
| Patch | GitHub · free5gc/pcf · Commit 52c33ddf |
| Report | GitHub · free5gc/free5gc · Issue #1181 |
| Report | GitHub · free5gc/free5gc · Issue #1184 |
| Repository | GitHub · free5gc/pcf · internal/sbi/processor/policyauthorization.go · L163-L385 |
| Link | vulncheck.com · advisories/free5gc-pcf-through-1.4.6-orphaned-pcc-rules-via-rejected-application-session-creation |
Questions about CVE-2026-133702
Is CVE-2026-133702 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-133702?
github.com/free5gc/pcf (Go): through 1.4.6.
Source: cve.now feed data
Related
- CVE-2026-42083free5GC: PCF Npcf_SMPolicyControl missing authentication middleware allows unauthenticated access to SM policy handlers and disclosure of subscriber SUPI
- CVE-2026-44316free5GC: PCF npcf-smpolicycontrol POST /sm-policies panics on downstream UDR/OpenAPI 404 via nil pointer dereference
- CVE-2026-41135free5GC PCF: Memory Leak via CORS Middleware Registration in HTTP Handler Leads to Denial of Service
- CVE-2026-44317free5GC: PCF npcf-policyauthorization POST /app-sessions panics on suppFeat=1 with missing AfRoutReq via nil pointer dereference
- CVE-2025-60632An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via crafted POST request to the Npcf_
- CVE-2026-1739Free5GC pcf smpolicy.go HandleCreateSmPolicyRequest null pointer dereference
No corrections so far. Something wrong on this page? Report an error.