CVE-2026-44316

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's PCF POST /npcf-smpolicycontrol/v1/sm-policies handler (HandleCreateSmPolicyRequest) panics with a nil-pointer dereference when a downstream OpenAPI consumer call (UDR lookup) returns 404 Not Found and the consumer wrapper returns err != nil together with a nil response struct. The handler logs the OpenAPI error and continues executing instead of returning, then dereferences the nil response struct on a subsequent line and panics. Gin recovery converts the panic into HTTP 500, so a single attacker-shaped POST returns 500 instead of a clean 4xx whenever the downstream lookup fails. The PCF process keeps running. The trigger is a single POST containing input that causes the downstream UDR lookup to fail (e.g. an unknown DNN). In 4.2.1 this endpoint is also reachable WITHOUT an Authorization header because the PCF Npcf_SMPolicyControl route group is mounted without inbound auth middleware. This vulnerability is fixed in 4.2.2.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
32.7%
KEV
Not listed

Published

May 27, 2026

Last Modified

May 28, 2026

Advisory Details (4)

Auto-updated Jun 6, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr.
generic

[Bugs]PCF crashes (nil pointer dereference) when CreateSmPolicy triggers downstream OpenAPI 404 (DoS) · Issue #803 · free5gc/free5gc · GitHub

https://github.com/free5gc/free5gc/issues/803
github_pr Patch Available

fix: smData mispositioned

Patch available: free5gc/pcf v1.4.2 (PR #62 merged 2026-01-21)

https://github.com/free5gc/pcf/pull/62
github_commit Patch Available

commit df535f552431 (free5gc/pcf)

Patch available: free5gc/pcf v1.4.2 (contains commit df535f552431)

https://github.com/free5gc/pcf/commit/df535f5524314620715e842baf9723efbeb481a7
github Patch Available🟡 PoC Available

PCF npcf-smpolicycontrol POST /sm-policies panics on downstream UDR/OpenAPI 404 via nil pointer dereference · Advisory · free5gc/free5gc · GitHub

https://github.com/free5gc/free5gc/security/advisories/GHSA-wr8j-6chw-gm6p

Vendor Advisories for CVE-2026-44316(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/free5gc/pcf—1.4.2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-24 14:05 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 40 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-15 17:49 UTCEPSS rescore
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-11 14:00 UTCEPSS rescore
  15. 2026-06-10 22:18 UTCEPSS rescore
  16. 2026-06-10 13:22 UTCEPSS rescore
  17. 2026-06-10 13:22 UTCEPSS rescore
  18. 2026-06-08 14:17 UTCEPSS rescore
  19. 2026-06-08 14:17 UTCEPSS rescore
  20. 2026-06-07 15:25 UTCEPSS rescore
  21. 2026-06-07 15:25 UTCEPSS rescore
  22. 2026-06-06 13:47 UTCEPSS rescore
  23. 2026-06-06 13:47 UTCEPSS rescore
  24. 2026-06-05 22:47 UTCEPSS rescore
  25. 2026-06-05 06:10 UTCEPSS rescore
  26. 2026-06-05 06:10 UTCEPSS rescore
  27. 2026-06-04 13:12 UTCEPSS rescore
  28. 2026-06-04 13:12 UTCEPSS rescore
  29. 2026-06-02 20:13 UTCEPSS rescore
  30. 2026-06-01 13:52 UTCEPSS rescore
  31. 2026-06-01 13:52 UTCEPSS rescore
  32. 2026-05-31 22:30 UTCEPSS rescore
  33. 2026-05-31 22:30 UTCEPSS rescore
  34. 2026-05-31 00:16 UTCEPSS rescore
  35. 2026-05-31 00:16 UTCEPSS rescore
  36. 2026-05-29 13:44 UTCEPSS rescore
  37. 2026-05-29 13:44 UTCEPSS rescore
  38. 2026-05-28 13:44 UTCEPSS rescore
  39. 2026-05-28 13:44 UTCEPSS rescore
  40. 2026-05-27 18:38 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44316?
CVE-2026-44316 is a high vulnerability published on May 27, 2026. free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's PCF POST /npcf-smpolicycontrol/v1/sm-policies handler (HandleCreateSmPolicyRequest) panics with a nil-pointer dereference when a downstream OpenAPI consumer call (UDR lookup) returns 404 Not Found and the…
When was CVE-2026-44316 disclosed?
CVE-2026-44316 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44316 actively exploited?
CVE-2026-44316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44316?
CVE-2026-44316 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44316, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44316

Explore →

Is Your Infrastructure Affected by CVE-2026-44316?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs