CVE-2026-44316

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 27, 2026

Last Modified

October 14, 2026

Advisory Details (4)

Auto-updated Jun 6, 2026
Patch available. Sources: github, github_commit, github_pr.
Web page

[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 pull request 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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
github.com/free5gc/pcf—
  • every version up to 1.4.2: fixed in 1.4.2
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 174 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-18 03:39 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-14 20:28 UTCEG score recompute
  8. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  11. 2026-10-12 16:05 UTCEG score recompute
  12. 2026-10-11 19:47 UTCEG score recompute
  13. 2026-10-11 17:02 UTCEG score recompute
  14. 2026-10-11 14:27 UTCEG score recompute
  15. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  18. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-10-03 16:49 UTCOSV refresh
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
Show 74 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  4. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-09-14 07:37 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-09-13 03:09 UTCOSV refresh
  13. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  27. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-08-25 05:15 UTCEG score recompute
  30. 2026-08-23 14:59 UTCEG score recompute
  31. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  32. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  33. 2026-08-21 20:32 UTCEG score recompute
  34. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  35. 2026-08-20 11:17 UTCEG score recompute
  36. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  37. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  39. 2026-08-16 15:13 UTCEG score recompute
  40. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  41. 2026-08-16 02:48 UTCEG score recompute
  42. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-08-14 01:25 UTCEG score recompute
  45. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-08-12 23:13 UTCEG score recompute
  47. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-08-12 00:47 UTCEG score recompute
  49. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  50. 2026-08-11 00:11 UTCEG score recompute
  51. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-08-09 19:40 UTCEG score recompute
  53. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  54. 2026-08-08 21:15 UTCEG score recompute
  55. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  56. 2026-08-07 17:56 UTCEG score recompute
  57. 2026-08-06 19:29 UTCEG score recompute
  58. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  59. 2026-08-05 20:52 UTCEG score recompute
  60. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  61. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  62. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  63. 2026-08-02 13:36 UTCEG score recompute
  64. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-08-01 15:10 UTCEG score recompute
  66. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  67. 2026-07-31 07:29 UTCEG score recompute
  68. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  69. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  70. 2026-07-29 15:03 UTCEG score recompute
  71. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  72. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  73. 2026-07-27 10:09 UTCEG score recompute
  74. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile

Frequently asked(5)

What is CVE-2026-44316?
CVE-2026-44316 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-44316 published?
The CVE record for CVE-2026-44316 was published on May 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-44316 actively exploited?
CVE-2026-44316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-44316 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44316 are linked in the Vendor Advisories panel on this page.

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.