Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

GHSA-f2hj-vpp9-6vm2

HIGHFix: free5gc/nssf@66fc727

GHSA-f2hj-vpp9-6vm2 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in github.com/free5gc/nssf. O3 Security confirms whether GHSA-f2hj-vpp9-6vm2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

NSSF panic due to nil pointer dereference when expiry field is omitted in NSSAIAvailability POST

Also known asCVE-2025-60638GO-2025-4163
Published
Nov 24, 2025
Updated
Dec 3, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Dec 3, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/free5gc/nssf

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

An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via crafted POST request to the Nnssf_NSSAIAvailability API.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/free5gc/nssfall versions1.4.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/nssf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/free5gc/nssf to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f2hj-vpp9-6vm2 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-f2hj-vpp9-6vm2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f2hj-vpp9-6vm2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in Free5GC v4.0.0 and v4.0.1 allowing an attacker to cause a denial of service via crafted POST request to the Nnssf_NSSAIAvailability API.
O3 Security · Impact-Aware SCA

Is GHSA-f2hj-vpp9-6vm2 in your dependencies?

O3 detects GHSA-f2hj-vpp9-6vm2 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-f2hj-vpp9-6vm2: nssf Denial of Service… | O3 Security