Vulnerability Database · Go · Package report

github.com/sagernet/smux: vulnerability history, versions and safety

github.com/sagernet/smux is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/sagernet/smux v1.5.50-sing-box-mod.1 i

Updated on 23 Oct 2026

Good news: v1.5.50-sing-box-mod.1, the version you would install today, has no known vulnerabilities.

Package health score 59/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v1.5.50-sing-box-mod.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.5.50-sing-box-mod.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.5.50-sing-box-mod.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3 i
  • OpenSSF scorecard 1/10 i
  • Last release 9 months ago i
  • Licence MIT 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/sagernet/smux, 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
v0.0.0-20260116181428-f373f1e706bf 16 Jan 2026 none MIT — Details →
v1.5.50-sing-box-mod.1 16 Jan 2026 none MIT — Details →
v0.0.0-20250505013534-e94cfacf2041 05 May 2025 none MIT — Details →
v1.5.34-mod.2 05 May 2025 none MIT — Details →
v0.0.0-20250430055335-1f51810ce6e5 30 Apr 2025 none MIT — Details →
v1.5.34-mod.1 30 Apr 2025 none MIT — Details →
v0.0.0-20250430054438-3feb85226b4f 30 Apr 2025 none MIT — Details →
v0.0.0-20231208180855-7041f6ea79e7 08 Dec 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230312102458-337ec2a5af37 12 Mar 2023 none GPL-3.0-or-later — Details →
v0.0.0-20220907034654-1acb8471c15a 07 Sep 2022 none GPL-3.0-or-later — Details →
v0.0.0-20220831015742-e0f1988e3195 31 Aug 2022 none GPL-3.0-or-later — Details →
v0.0.0-20220812084127-e2d085ee3939 12 Aug 2022 none GPL-3.0-or-later — Details →
v0.0.0-20220812082841-d1c2b4473617 12 Aug 2022 none GPL-3.0-or-later — Details →
v0.0.0-20220812032842-6d45eecb473e 12 Aug 2022 none GPL-3.0-or-later — Details →
v0.0.0-20220620140142-942de9a65e94 20 Jun 2022 none GPL-3.0-or-later — Details →
v0.0.0-20220620024907-e3e5a7d0806b 20 Jun 2022 none GPL-3.0-or-later — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for github.com/sagernet/smux

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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/sagernet/smux

Is github.com/sagernet/smux safe to use?

Vulert has no vulnerabilities on record for github.com/sagernet/smux in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is github.com/sagernet/smux's Vulert package health score?

Vulert scores github.com/sagernet/smux 59/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/sagernet/smux affected?

No. v1.5.50-sing-box-mod.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of github.com/sagernet/smux should I use?

v1.5.50-sing-box-mod.1 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/sagernet/smux have?

0 vulnerabilities are recorded for github.com/sagernet/smux in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/sagernet/smux vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/sagernet/smux in the last 12 months. 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/sagernet/smux 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/sagernet/smux for upcoming vulnerabilities?

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