CVE-2026-44315
RCE in free5GC NEF API via forged tokens (pre-4.2.2).
Is CVE-2026-44315 being exploited?
Not confirmed. CVE-2026-44315 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-44315?
CVE-2026-44315 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44315?
Yes. A fix has been recorded for CVE-2026-44315. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44315 affect?
CVE-2026-44315 affects free5GC NEF (pre-4.2.2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44315?
Upgrade to 4.2.2+; enforce OAuth2; restrict NEF access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can create/read/delete PFD-management state via forged Bearer tokens over SBI; exposure enables further compromise.
Patch when possible
- affected< 4.2.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.