VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/sagernet/gomobile 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.

See all github.com/sagernet/gomobile vulnerabilities

Vulert verdict on github.com/sagernet/gomobile v0.1.13 i

Updated on 23 Oct 2026

Good news: v0.1.13, the version you would install today, has no known vulnerabilities.

Package health score 74/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on v0.1.13 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.13 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.1.13 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 21 i
  • Last release 4 months ago i
  • Licence BSD-3-Clause 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/gomobile, 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.1.13 11 Jun 2026 none BSD-3-Clause — Details →
v0.1.12 27 Feb 2026 none BSD-3-Clause — Details →
v0.1.12-0.20260113115337-fb7f31af3f48 13 Jan 2026 none BSD-3-Clause — Details →
v0.1.12-0.20260113033731-6af310f65ee2 13 Jan 2026 none BSD-3-Clause — Details →
v0.1.12-0.20260112141305-b2f5677d49d7 12 Jan 2026 none BSD-3-Clause — Details →
v0.1.12-0.20260111141336-2bce4d211c59 11 Jan 2026 none BSD-3-Clause — Details →
v0.1.11 06 Jan 2026 none BSD-3-Clause — Details →
v0.1.10 13 Dec 2025 none BSD-3-Clause — Details →
v0.1.9 12 Dec 2025 none BSD-3-Clause — Details →
v0.1.9-0.20251212103248-3dff81649a55 12 Dec 2025 none BSD-3-Clause — Details →
v0.1.8 13 Aug 2025 none BSD-3-Clause — Details →
v0.0.0-20250703120613-866b92cf1d23 03 Jul 2025 none BSD-3-Clause — Details →
v0.1.7 03 Jul 2025 none BSD-3-Clause — Details →
v0.1.6 02 Apr 2025 none BSD-3-Clause — Details →
v0.1.5 21 Mar 2025 none BSD-3-Clause — Details →
v0.1.4 10 Sep 2024 none BSD-3-Clause — Details →
v0.1.3 24 Feb 2024 none BSD-3-Clause — Details →
v0.1.2 24 Feb 2024 none BSD-3-Clause — Details →
v0.1.1 09 Dec 2023 none BSD-3-Clause — Details →
v0.0.0-20231208173245-0e138e983102 08 Dec 2023 none BSD-3-Clause — Details →
v0.1.0 08 Dec 2023 none BSD-3-Clause — Details →
v0.0.0-20231208172717-1ea91e4cf841 08 Dec 2023 none BSD-3-Clause — Details →
v0.0.0-20230915142329-c6740b6d2950 15 Sep 2023 none BSD-3-Clause — Details →
v0.0.0-20230728014906-3de089147f59 28 Jul 2023 none BSD-3-Clause — Details →
v0.0.0-20230701084532-493ee2e45182 01 Jul 2023 none BSD-3-Clause — Details →
v0.0.0-20230701065244-4158c3539e5c 01 Jul 2023 none BSD-3-Clause — Details →
v0.0.0-20230630063748-2e980714df6a 30 Jun 2023 none BSD-3-Clause — Details →
v0.0.0-20230630063059-6ac5886042a9 30 Jun 2023 none BSD-3-Clause — Details →
v0.0.0-20230630062453-429af83f4784 30 Jun 2023 none BSD-3-Clause — Details →
v0.0.0-20230630060327-9e17cd6458ab 30 Jun 2023 none BSD-3-Clause — Details →
v0.0.0-20230630060045-1b3be4470634 30 Jun 2023 none BSD-3-Clause — Details →
v0.0.0-20230630055222-20b0b791c616 30 Jun 2023 none BSD-3-Clause — Details →
v0.0.0-20230413023804-244d7ff07035 13 Apr 2023 none BSD-3-Clause — Details →
v0.0.0-20230413023437-ec061884b992 13 Apr 2023 none BSD-3-Clause — Details →
v0.0.0-20221130124640-349ebaa752ca 30 Nov 2022 none BSD-3-Clause — Details →
v0.0.0-20221130123945-26a9dde52edd 30 Nov 2022 none BSD-3-Clause — Details →
v0.0.0-20221025042457-7e85203750eb 25 Oct 2022 none BSD-3-Clause — Details →
v0.0.0-20220616115759-d86e1a4931f0 16 Jun 2022 none BSD-3-Clause — Details →
v0.0.0-20220616115322-8f81ed8881cc 16 Jun 2022 none BSD-3-Clause — Details →
v0.0.0-20220214172500-89df302623c8 14 Feb 2022 none BSD-3-Clause — Details →
v0.0.0-20220214170642-6ed0baa9cad9 14 Feb 2022 none BSD-3-Clause — Details →
v0.0.0-20220214165715-3fc86b301731 14 Feb 2022 none BSD-3-Clause — Details →
v0.0.0-20220214165046-27df8f5c9674 14 Feb 2022 none BSD-3-Clause — Details →
v0.0.0-20220214163550-2e0161e57f6a 14 Feb 2022 none BSD-3-Clause — Details →
v0.0.0-20210905032500-701a995ff844 05 Sep 2021 none BSD-3-Clause — Details →
v0.0.0-20210822074701-68a55075c7d2 22 Aug 2021 none BSD-3-Clause — Details →
v0.0.0-20210822074050-2531a01f9753 22 Aug 2021 none BSD-3-Clause — Details →
v0.0.0-20210822072414-c379ce385f6a 22 Aug 2021 none BSD-3-Clause — Details →
v0.0.0-20210822065406-9cd1ff113ebd 22 Aug 2021 none BSD-3-Clause — Details →

All 49 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/gomobile

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/gomobile

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

Vulert has no vulnerabilities on record for github.com/sagernet/gomobile 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/gomobile's Vulert package health score?

Vulert scores github.com/sagernet/gomobile 74/100, which reads as in good shape. 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/gomobile affected?

No. v0.1.13, 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/gomobile should I use?

v0.1.13 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/gomobile have?

0 vulnerabilities are recorded for github.com/sagernet/gomobile 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/gomobile vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/sagernet/gomobile 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/gomobile 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/gomobile for upcoming vulnerabilities?

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