How severe is GHSA-7c47-xr7q-p6hg?

No CVSS score has been assigned to GHSA-7c47-xr7q-p6hg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7c47-xr7q-p6hg?

GHSA-7c47-xr7q-p6hg affects the following packages: github.com/free5gc/nrf (Go). Ecosystems affected: Go.

How do I fix GHSA-7c47-xr7q-p6hg?

Update github.com/free5gc/nrf to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7c47-xr7q-p6hg is resolved across your whole dependency graph.

How do I detect GHSA-7c47-xr7q-p6hg in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/nrf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-7c47-xr7q-p6hg if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-7c47-xr7q-p6hg actively exploited in the wild?

No public exploit code has been indexed for GHSA-7c47-xr7q-p6hg 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-7c47-xr7q-p6hg?

GHSA-7c47-xr7q-p6hg has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th 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-7c47-xr7q-p6hg?

GHSA-7c47-xr7q-p6hg is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7c47-xr7q-p6hg published, and has it been updated?

GHSA-7c47-xr7q-p6hg 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

free5GC NRF Discovery EncodeGroupId Function Panics on Malformed group-id-list ParameterGHSA-7c47-xr7q-p6hg

Fix: free5gc/nrf#80

GHSA-7c47-xr7q-p6hg is a CWE-284 vulnerability in github.com/free5gc/nrf. A fix is available for github.com/free5gc/nrf — see the affected versions and patch details below.

Also known asCVE-2026-33062GO-2026-4756

Published

Mar 18, 2026

Updated

Mar 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 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-7c47-xr7q-p6hg.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/free5gc/nrf

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 Input Validation vulnerability leading to Denial of Service.

Security Impact: A remote attacker can cause the NRF service to panic and crash by sending a crafted HTTP GET request with a malformed group-id-list parameter. This results in complete denial of service for the NRF discovery service.
Functional Impact: The EncodeGroupId function attempts to access array indices [0], [1], [2] without validating the length of the split data. When the parameter contains insufficient separator characters, the code panics with "index out of range".
Affected Parties: All deployments of free5GC v4.0.1 using the NRF discovery service.

Patches
Yes, the issue has been patched.
The fix is implemented in PR free5gc/nrf#80 (commit: [add fix reference here]).
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 NRF API to trusted sources only.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

free5gcfree5gc

< 1.4.2

range

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/nrf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/free5gc/nrf to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7c47-xr7q-p6hg is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

**Impact** This is an Improper Input Validation vulnerability leading to Denial of Service. - **Security Impact**: A remote attacker can cause the NRF service to panic and crash by sending a crafted HTTP GET request with a malformed `group-id-list` parameter. This results in complete denial of service for the NRF discovery service. - **Functional Impact**: The `EncodeGroupId` function attempts to access array indices [0], [1], [2] without validating the length of the split data. When the parameter contains insufficient separator characters, the code panics with "index out of range". -

O3 Security · Impact-Aware SCA

Is GHSA-7c47-xr7q-p6hg in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works