Is github.com/free5gc/nef 1.1 vulnerable?
Go · 1 release from 1.1.0 to 1.1.0 · latest github.com/free5gc/nef is 1.2.6 · checked 18 Nov 2026
Yes: 14 known advisories
Yes. github.com/free5gc/nef 1.1.0, the last 1.1 release, is affected by 14 known security advisories (4 critical, 3 high, 7 low), including CVE-2026-44330, CVE-2026-44327, CVE-2026-44326. At least one has no fixed release yet.
Is your project on an affected github.com/free5gc/nef?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/free5gc/nef 1.1.0
free5GC's NEF nnef-pfdmanagement API is unauthenticated; forged bearer tokens can read PFD data and create/delete PFD subscriptions in github.com/free5gc/nef
- Affected
- All versions
- Fixed in
- No fix released
free5GC's NEF crashes via logger.Fatal on PFD notification delivery failure (attacker-controlled notifyUri) in github.com/free5gc/nef
- Affected
- <1.2.3
- Fixed in
- 1.2.3
free5GC's NEF nnef-callback route group is unauthenticated; forged callback requests are accepted into the processing path in github.com/free5gc/nef
- Affected
- All versions
- Fixed in
- No fix released
free5GC's NEF 3gpp-pfd-management PATCH applications/{appId} panics on UDR access failure due to nil ProblemDetails dereference in github.com/free5gc/nef
- Affected
- <1.2.3
- Fixed in
- 1.2.3
free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler in github.com/free5gc/nef
- Affected
- All versions
- Fixed in
- No fix released
free5GC's NEF 3gpp-traffic-influence API is unauthenticated; missing or forged bearer tokens can create, read, patch, and delete subscriptions in github.com/free5gc/nef
- Affected
- All versions
- Fixed in
- No fix released
free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions in github.com/free5gc/nef
- Affected
- All versions
- Fixed in
- No fix released
free5GC's NEF nnef-pfdmanagement API is unauthenticated; forged bearer tokens can read PFD data and create/delete PFD subscriptions
- Affected
- <=1.2.3
- Fixed in
- No fix released
free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler
- Affected
- <=1.2.3
- Fixed in
- No fix released
free5GC's NEF 3gpp-traffic-influence API is unauthenticated; missing or forged bearer tokens can create, read, patch, and delete subscriptions
- Affected
- <=1.2.3
- Fixed in
- No fix released
free5GC's NEF 3gpp-pfd-management PATCH applications/{appId} panics on UDR access failure due to nil ProblemDetails dereference
- Affected
- <1.2.3
- Fixed in
- 1.2.3
free5GC's NEF nnef-callback route group is unauthenticated; forged callback requests are accepted into the processing path
- Affected
- <=1.2.3
- Fixed in
- No fix released
free5GC's NEF crashes via logger.Fatal on PFD notification delivery failure (attacker-controlled notifyUri)
- Affected
- <1.2.3
- Fixed in
- 1.2.3
free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions
- Affected
- <=1.2.3
- Fixed in
- No fix released
Which of your client projects are still on github.com/free5gc/nef 1.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/free5gc/nef version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/free5gc/nef versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.