Quick answers
- Is CVE-2026-94043 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94043 being exploited in the wild.
- How severe is CVE-2026-94043?
- Medium severity, with a CVSS score of 5.3, published 20 September 2026.
- Which products and versions are affected?
- free5GC up to 4.2.3.
- Is there a fix for CVE-2026-94043?
- A patch was published on 2026-08-27: Commit e323b01 merged Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94043 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-94043?
- Check whether you run free5GC 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 race condition in the GMM handler's RanUe context management within Free5GC's AMF component. The RanUe map was accessed without proper synchronization (mutex protection), allowing concurrent read/write operations to corrupt shared state. The fix adds a sync.RWMutex (ranUeMu) to serialize access to the RanUe context map, eliminating the data race.
Affected products
- Free5GC Free5GC up to 4.2.3
Timeline
- 2026-09-20: disclosed
- 2026-08-27: patched: Commit e323b01 merged