VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/free5gc/nssf: vulnerability history, versions and safety

github.com/free5gc/nssf is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 38 releases, from Nov 2025 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 02 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/free5gc/nssf vulnerabilities

Vulert verdict on github.com/free5gc/nssf v1.4.6 i

Updated on 23 Oct 2026

Action needed: v1.4.6 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 62/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.4.6 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 02 Dec 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 7 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/free5gc/nssf, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.4.7-0.20261015043935-70ebaf8d5441 15 Oct 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.6 19 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.6-0.20260819160730-c1092f6f865d 19 Aug 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.6-0.20260707005357-283f549ed90b 07 Jul 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.4 11 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.5 11 May 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.3 13 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.3-0.20260413004955-08e84c3912e8 13 Apr 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.2 29 Jan 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.1 04 Jan 2026 H1 U1 Apache-2.0 Yes Details →
v1.4.1-0.20251124083153-fb3c99f15228 24 Nov 2025 H1 U1 Apache-2.0 Yes Details →
v1.4.1-0.20250916111159-f469ded6cf75 16 Sep 2025 H1 U1 Apache-2.0 Yes Details →
v1.4.0 15 Aug 2025 H1 U1 Apache-2.0 Yes Details →
v1.3.3-0.20250815092146-66fc727a894f 15 Aug 2025 H1 U1 Apache-2.0 Yes Details →
v1.3.3-0.20250814102020-3bb6990799f3 14 Aug 2025 H1 U1 Apache-2.0 Yes Details →
v1.3.3-0.20250718143423-872b2c8798c6 18 Jul 2025 H1 U1 Apache-2.0 Yes Details →
v1.3.2 17 Apr 2025 H1 U1 Apache-2.0 Yes Details →
v1.3.1 03 Mar 2025 H1 U1 Apache-2.0 Yes Details →
v1.2.4 02 Jan 2025 H1 U1 Apache-2.0 Yes Details →
v1.2.4-0.20250102025607-002ee94c1b44 02 Jan 2025 H1 U1 Apache-2.0 Yes Details →
v1.2.3 27 Jun 2024 H1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20240627054402-a73f10ff6d71 27 Jun 2024 H1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20240423010935-574d044bd173 23 Apr 2024 H1 U1 Apache-2.0 Yes Details →
v1.2.2 27 Mar 2024 H1 U1 Apache-2.0 Yes Details →
v1.2.2-0.20240314005003-d9e37d79c8cb 14 Mar 2024 H1 U1 Apache-2.0 Yes Details →
v1.2.1 07 Feb 2024 H1 U1 Apache-2.0 Yes Details →
v1.2.1-0.20231219091825-83ee4874cbd4 19 Dec 2023 H1 U1 Apache-2.0 Yes Details →
v1.2.1-0.20231012123742-0217fbcf238b 12 Oct 2023 H1 U1 Apache-2.0 Yes Details →
v1.2.1-0.20231001101635-8d35182aa9a7 01 Oct 2023 H1 U1 Apache-2.0 Yes Details →
v1.2.1-0.20230823154344-ced53b7bb3c7 23 Aug 2023 H1 U1 Apache-2.0 Yes Details →
v1.1.1 02 May 2022 H1 U1 Apache-2.0 Yes Details →
v1.1.1-0.20220502152724-04037a7a8065 02 May 2022 H1 U1 Apache-2.0 Yes Details →
v1.1.1-0.20220407155145-9ab2a7e381da 07 Apr 2022 H1 U1 Apache-2.0 Yes Details →
v1.0.2 27 Dec 2021 H1 U1 Apache-2.0 Yes Details →
v1.0.1 30 Jul 2021 H1 U1 Apache-2.0 Yes Details →
v1.0.0 30 Jan 2021 H1 U1 Apache-2.0 Yes Details →
v1.3.0 18 Jan 2021 H1 U1 Apache-2.0 Yes Details →
v0.0.0-20201124123259-e059d774dbff 24 Nov 2020 H1 U1 Apache-2.0 Yes Details →

All 38 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/free5gc/nssf

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-60638: Free5GC NSSF Nil Pointer Dereference Vulnerability 7.5 high 1.4.0 24 Nov 2025
CVE-2025-60638: NSSF Nil Pointer Dereference Vulnerability in github.com/free5gc/nssf N/A unrated 1.4.0 02 Dec 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/free5gc/nssf

Is github.com/free5gc/nssf safe to use?

Vulert records 2 vulnerabilities for github.com/free5gc/nssf in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/free5gc/nssf's Vulert package health score?

Vulert scores github.com/free5gc/nssf 62/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/free5gc/nssf affected?

Yes. v1.4.6, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/free5gc/nssf should I use?

v1.4.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/free5gc/nssf have?

2 vulnerabilities are recorded for github.com/free5gc/nssf in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/free5gc/nssf vulnerabilities disclosed?

2 vulnerabilities were recorded for github.com/free5gc/nssf in the last 12 months, and the oldest entry in this database dates to 24 Nov 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/free5gc/nssf are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/free5gc/nssf for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/free5gc/nssf version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.