How severe is GHSA-4jrw-92fg-4jwx?

No CVSS score has been assigned to GHSA-4jrw-92fg-4jwx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4jrw-92fg-4jwx?

GHSA-4jrw-92fg-4jwx affects the following packages: github.com/free5gc/ausf (Go). Ecosystems affected: Go.

How do I fix GHSA-4jrw-92fg-4jwx?

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 GHSA-4jrw-92fg-4jwx is resolved across your whole dependency graph.

How do I detect GHSA-4jrw-92fg-4jwx in my Go dependencies?

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.

How do I mitigate GHSA-4jrw-92fg-4jwx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4jrw-92fg-4jwx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4jrw-92fg-4jwx can be triaged on real exposure rather than presence alone.

Is GHSA-4jrw-92fg-4jwx actively exploited in the wild?

No public exploit code has been indexed for GHSA-4jrw-92fg-4jwx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4jrw-92fg-4jwx?

GHSA-4jrw-92fg-4jwx has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4jrw-92fg-4jwx?

GHSA-4jrw-92fg-4jwx is classified as NULL Pointer Dereference (CWE-476). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4jrw-92fg-4jwx published, and has it been updated?

GHSA-4jrw-92fg-4jwx was published on March 18, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-4jrw-92fg-4jwx — ausf

Fix: free5gc/ausf#52

GHSA-4jrw-92fg-4jwx 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

Also known asCVE-2026-33063GO-2026-4754

Published

Mar 18, 2026

Updated

Mar 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-4jrw-92fg-4jwx.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/free5gc/ausf

Real-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 GetSupiFromSuciSupiMap function. This results in complete denial of service for the AUSF authentication service.
Functional Impact: The GetSupiFromSuciSupiMap function attempts to perform an interface conversion from interface{} to *context.SuciSupiMap without checking if the underlying value is nil. When SuciSupiMap is 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-authentications endpoint).

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/free5gc/ausf`	all versions	1.4.2`go get github.com/free5gc/ausf@v1.4.2`

Detection & mitigation playbook

Open-source dependency

Detect
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 GHSA-4jrw-92fg-4jwx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4jrw-92fg-4jwx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4jrw-92fg-4jwx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**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 `GetSupiFromSuciSupiMap` function. This results in complete denial of service for the AUSF authentication service. - **Functional Impact**: The `GetSupiFromSuciSupiMap` function attempts to perform an interface conversion from `interface{}` to `*context.SuciSupiMap` without checking if the underlying value is nil. When `Suci

O3 Security · Impact-Aware SCA

Is GHSA-4jrw-92fg-4jwx in your dependencies?

O3 Security finds GHSA-4jrw-92fg-4jwx across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works