Free5GC AMF is vulnerable to DoS through its HandleRegistrationComplete functionGHSA-xq44-64rg-8g3h
MEDIUMFix: free5gc/amf#198GHSA-xq44-64rg-8g3h is a medium-severity (CVSS 5.3) CWE-404 vulnerability in github.com/free5gc/amf. A fix is available for github.com/free5gc/amf — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xq44-64rg-8g3h.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/free5gc/amfReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A weakness has been identified in Free5GC 4.1.0. Affected is the function HandleRegistrationComplete of the file internal/gmm/handler.go of the component AMF. Executing a manipulation can lead to denial of service. The attack may be performed from remote. This patch is called 52e9386401ce56ea773c5aa587d4cdf7d53da799. It is best practice to apply a patch to resolve this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/free5gc/amf | all versions | 1.4.3-0.20260306074636-52e9386401cego get github.com/free5gc/amf@v1.4.3-0.20260306074636-52e9386401ce |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/amf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/free5gc/amf to 1.4.3-0.20260306074636-52e9386401ce or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq44-64rg-8g3h is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-xq44-64rg-8g3h in your dependencies?
Find it across Go, including transitive dependencies.