CVE-2026-33063 — ausf
Fix: free5gc/ausf@3b9ac44CVE-2026-33063 is a NULL Pointer Dereference vulnerability in github.com/free5gc/ausf. A fix is available for github.com/free5gc/ausf — see the affected versions and patch details below.
free5GC AUSF UE Authentication Panic on Nil SuciSupiMap Interface Conversion
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33063.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/free5gc/ausfReal-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
Impact
This is an Improper Null Check vulnerability leading to Denial of Service.
- Security Impact: A remote attacker can cause the AUSF service to panic and crash by sending a crafted UE authentication request that triggers a nil interface conversion in the
GetSupiFromSuciSupiMapfunction. This results in complete denial of service for the AUSF authentication service. - Functional Impact: The
GetSupiFromSuciSupiMapfunction attempts to perform an interface conversion frominterface{}to*context.SuciSupiMapwithout checking if the underlying value is nil. WhenSuciSupiMapis nil, the code panics with "interface conversion: interface {} is nil, not *context.SuciSupiMap". - Affected Parties: All deployments of free5GC v4.0.1 using the AUSF UE authentication service (
/nausf-auth/v1/ue-authenticationsendpoint).
Patches
Yes, the issue has been patched.
The fix is implemented in PR free5gc/ausf#52 (commit: [add specific commit hash if available]).
Users should upgrade to the next release of free5GC that includes this commit.
Workarounds
There is no direct workaround at the application level. The recommendation is to apply the provided patch or restrict access to the AUSF API to trusted sources only.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/free5gc/ausf | all versions | 1.4.2go get github.com/free5gc/ausf@v1.4.2 |
Affected Products
free5gcfree5gcDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/ausf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/free5gc/ausf to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33063 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 CVE-2026-33063 in your dependencies?
Find it across Go, including transitive dependencies.