How severe is GHSA-6rgm-gr97-x3j5?

GHSA-6rgm-gr97-x3j5 has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6rgm-gr97-x3j5?

GHSA-6rgm-gr97-x3j5 affects the following packages: github.com/free5gc/pcf (Go). Ecosystems affected: Go.

How do I fix GHSA-6rgm-gr97-x3j5?

Update github.com/free5gc/pcf to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rgm-gr97-x3j5 is resolved across your whole dependency graph.

How do I detect GHSA-6rgm-gr97-x3j5 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/pcf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6rgm-gr97-x3j5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6rgm-gr97-x3j5?

O3 pinpoints whether GHSA-6rgm-gr97-x3j5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6rgm-gr97-x3j5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6rgm-gr97-x3j5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6rgm-gr97-x3j5 published, and has it been updated?

GHSA-6rgm-gr97-x3j5 was published on May 7, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

GHSA-6rgm-gr97-x3j5

HIGHFix: free5gc/pcf#63

GHSA-6rgm-gr97-x3j5 is a high-severity (CVSS 8.2) vulnerability in github.com/free5gc/pcf. O3 Security confirms whether GHSA-6rgm-gr97-x3j5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Free5GC PCF: Missing authentication middleware in Npcf_SMPolicyControl allows access to SM policy handlers and disclosure of subscriber SUPI

Also known asCVE-2026-42083GO-2026-5189

Published

May 7, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/free5gc/pcf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

PCF Npcf_SMPolicyControl missing authentication middleware allows unauthenticated access to SM policy handlers and disclosure of subscriber SUPI

Details

In NewServer(), the smPolicyGroup route group is created and routes are applied without attaching the router authorization middleware. In contrast, other PCF service groups such as Npcf_PolicyAuthorization do attach RouterAuthorizationCheck before route registration.

Because the middleware is missing, requests to the following endpoints can reach business logic even when no valid OAuth token is provided:

POST /npcf-smpolicycontrol/v1/sm-policies
GET /npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}
POST /npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}/update
POST /npcf-smpolicycontrol/v1/sm-policies/{smPolicyId}/delete

This is visible at runtime because unauthenticated requests return business-level responses such as 400 or 404 instead of being rejected with 401 before handler execution. Under valid lab preconditions (existing UE/session context and related policy data), unauthenticated POST /sm-policies can succeed with 201, and unauthenticated GET /sm-policies/{id} can succeed with 200 and return policy context containing subscriber identifiers including supi.

The root cause is missing router auth enforcement for Npcf_SMPolicyControl. Upstream also fixed this by adding RouterAuthorizationCheck to smPolicyGroup (and uePolicyGroup) in free5gc/pcf PR #63.

PoC

Deploy free5GC with PCF reachable on the SBI network.

Use the PoC against the PCF service without an Authorization header:

go run /home/ubuntu/free5gc/tools/npcf-smpolicy-noauth-poc/main.go \
  --pcf-root /home/ubuntu/free5gc/NFs/pcf \
  --pcf-url http://10.100.200.9:8000 \
  --timeout 4s

Observe that unauthenticated requests to Npcf_SMPolicyControl return business responses instead of 401.

Impact

This is an authentication/authorization bypass on a network-accessible SBI service. Any unauthenticated actor able to reach the PCF SBI interface can invoke Npcf_SMPolicyControl handlers directly.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/free5gc/pcf`	all versions	1.4.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/pcf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/free5gc/pcf to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6rgm-gr97-x3j5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6rgm-gr97-x3j5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6rgm-gr97-x3j5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary PCF Npcf_SMPolicyControl missing authentication middleware allows unauthenticated access to SM policy handlers and disclosure of subscriber SUPI ### Details In `NewServer()`, the `smPolicyGroup` route group is created and routes are applied without attaching the router authorization middleware. In contrast, other PCF service groups such as `Npcf_PolicyAuthorization` do attach `RouterAuthorizationCheck` before route registration. Because the middleware is missing, requests to the following endpoints can reach business logic even when no valid OAuth token is provided: - `POST /npcf

O3 Security · Impact-Aware SCA

Is GHSA-6rgm-gr97-x3j5 in your dependencies?

O3 detects GHSA-6rgm-gr97-x3j5 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works