# CVE-2026-30072: free5gc CHF NULL pointer dereference in CDR processing

Source: https://junglewise.ai/threats/cve-2026-30072-free5gc-chf-null-pointer-dereference-in-cdr-processing  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-27. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-30072 · Severity: high · CVSS 7.5 · Published 2026-08-27

free5gc is an open-source implementation of a 5G core network. The Charging Handling Function (CHF) component processes billing data from other network functions. A NULL pointer dereference vulnerability in the CDR (Charge Detail Record) processing path allows an attacker to crash the CHF service by sending a malformed charging request, disrupting billing operations and network service availability.

Vendors: [free5GC](https://junglewise.ai/threats/vendors/free5gc).

## Quick answers

**Is CVE-2026-30072 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-30072 being exploited in the wild.

**How severe is CVE-2026-30072?** High severity, with a CVSS score of 7.5, published 27 August 2026.

**Which products and versions are affected?** free5GC CHF (Charging Handling Function) v4.0.1.

**Is there a fix for CVE-2026-30072?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-30072 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-30072?** Check whether you run free5GC CHF (Charging Handling Function) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a NULL pointer dereference in the OpenCDR function within internal/sbi/processor/cdr.go of free5gc v4.0.1. The code assumes the nested field pDUSessionChargingInformation.pduSessionInformation is non-nil and directly accesses PduSessionInformation.PduSessionID without prior validation. When a client omits the pduSessionInformation field in a POST request to /nchf-convergedcharging/v3/chargingdata, the code dereferences a nil pointer, causing a runtime panic. The vulnerability is network-reachable and requires no authentication; an attacker can trigger it by sending a crafted JSON payload via HTTP POST. The impact is Denial of Service—the CHF process crashes and returns HTTP 500 or drops the connection, halting billing functions.

## Affected products

- free5gc CHF (Charging Handling Function) v4.0.1

## Timeline

- 2026-01-01: disclosed: Issue reported on GitHub
- 2026-08-27: advisory: CVE-2026-30072 published

## References

- [https://github.com/free5gc/free5gc/issues/759](https://github.com/free5gc/free5gc/issues/759)