# CVE-2026-1739: Free5GC pcf smpolicy.go HandleCreateSmPolicyRequest null pointer dereference

> Remote attackers can cause a denial of service in Free5GC PCF via a null pointer dereference in the SM policy handler.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-659g-9v9q-gq45

## What is CVE-2026-1739?

CVE-2026-1739 is a medium-severity vulnerability in Free5GC pcf, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in Free5GC pcf up to 1.4.1. This affects the function HandleCreateSmPolicyRequest of the file internal/sbi/processor/smpolicy.go. The manipulation leads to null pointer dereference. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. The identifier of the patch is df535f5524314620715e842baf9723efbeb481a7. Applying a patch is the recommended action to fix this issue.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2026-1739?

It affects 1 product.


Products: Free5gc Pcf.

## How do I fix CVE-2026-1739?

No fix has been published for CVE-2026-1739 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1739 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1739 exists.

## Other vulnerabilities in Free5GC pcf

- [CVE-2025-66720](https://insights.sbomify.com/CVE-2025-66720/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1739 and fix it if it is affected.

What it is: CVE-2026-1739 is a medium-severity vulnerability in Free5GC pcf, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1739 exists.

Affected product: Free5GC pcf. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1739/ (Markdown: https://insights.sbomify.com/CVE-2026-1739/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1739
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1739
- OSV: https://osv.dev/vulnerability/CVE-2026-1739

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1739/
Summaries are generated and may contain mistakes; the official description above is the record.