A vulnerability was determined in Free5GC up to 4.2.3. This vulnerability affects unknown code of the file /corefuzzer_deps/free5gc/NFs/amf/internal/gmm/handler.go of the component Gmm Handler. This manipulation causes race condition. The attack can be initiated remotely. Patch name: e323b01464355781b8b8d5dd695e05cbc00a62f2. To fix this issue, it is recommended to deploy a patch.
CVE-2026-94043
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 20, 2026
Last Modified
September 20, 2026
Advisory Details (4)
Auto-updated Sep 20, 2026GitHub - free5gc/free5gc: Open source 5G core network based on 3GPP R17 · GitHub
https://github.com/free5gc/free5gc/commit e323b0146435 (free5gc/amf)
Fix landed in free5gc/amf commit e323b0146435 — awaiting tagged release
https://github.com/free5gc/amf/commit/e323b01464355781b8b8d5dd695e05cbc00a62f2fix: synchronize RanUe context access
Upstream fix in progress (PR #238 · free5gc/amf, state=open)
https://github.com/free5gc/amf/pull/238[Bugs] AMF crash with fatal error: concurrent map read and map write when RegistrationRequest races with SCTP shutdown · Issue #1109 · free5gc/free5gc · GitHub
https://github.com/free5gc/free5gc/issues/1109Vendor Advisories for CVE-2026-94043(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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.
- 2026-09-20 19:20 UTCEG score recompute
- 2026-09-20 19:19 UTCNVD updateCVSS v4 → 5.5
- 2026-09-20 18:21 UTCEG score recompute
- 2026-09-20 18:21 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-94043?
When was CVE-2026-94043 disclosed?
What is the CVSS score of CVE-2026-94043?
How do I remediate CVE-2026-94043?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-94043
Is Your Infrastructure Affected by CVE-2026-94043?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.