VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/v2fly/v2ray-core: vulnerability history, versions and safety

github.com/v2fly/v2ray-core is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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/v2fly/v2ray-core vulnerabilities

Vulert verdict on github.com/v2fly/v2ray-core v4.15.0+incompatible i

Updated on 22 Oct 2026

Careful: v4.15.0+incompatible has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v4.15.0+incompatible — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 21 Aug 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 34,685 i
  • OpenSSF scorecard 5/10 i
  • Last release 92 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/v2fly/v2ray-core, 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
v4.15.0+incompatible 07 Feb 2019 U1 MIT No Details →
v4.14.2+incompatible 06 Feb 2019 U1 MIT No Details →
v4.14.1+incompatible 06 Feb 2019 U1 MIT No Details →
v4.14.0+incompatible 30 Jan 2019 U1 MIT No Details →
v4.13.0+incompatible 17 Jan 2019 U1 MIT No Details →
v4.12.0+incompatible 12 Jan 2019 U1 MIT No Details →
v4.11.0+incompatible 10 Jan 2019 U1 MIT No Details →
v4.10.0+incompatible 03 Jan 2019 U1 MIT No Details →
v4.9.0+incompatible 11 Dec 2018 U1 MIT No Details →
v4.8.0+incompatible 06 Dec 2018 U1 MIT No Details →
v4.7.3+incompatible 04 Dec 2018 U1 MIT No Details →
v4.7.2+incompatible 04 Dec 2018 U1 MIT No Details →
v4.7.1+incompatible 04 Dec 2018 U1 MIT No Details →
v4.7.0+incompatible 29 Nov 2018 U1 MIT No Details →
v4.6.6+incompatible 27 Nov 2018 U1 MIT No Details →
v4.6.5+incompatible 25 Nov 2018 U1 MIT No Details →
v4.6.4+incompatible 24 Nov 2018 U1 MIT No Details →
v4.6.3+incompatible 23 Nov 2018 U1 MIT No Details →
v4.6.2+incompatible 23 Nov 2018 U1 MIT No Details →
v4.6.1+incompatible 23 Nov 2018 U1 MIT No Details →
v4.6.0+incompatible 22 Nov 2018 U1 MIT No Details →
v4.5.0+incompatible 16 Nov 2018 U1 MIT No Details →
v4.1.1+incompatible 05 Nov 2018 U1 MIT No Details →
v4.0.2+incompatible 04 Nov 2018 U1 MIT No Details →
v4.0.1+incompatible 03 Nov 2018 U1 MIT No Details →
v3.50.2+incompatible 29 Oct 2018 U1 MIT No Details →
v3.50.1+incompatible 28 Oct 2018 U1 MIT No Details →
v3.46.3+incompatible 06 Oct 2018 U1 MIT No Details →
v3.46.4+incompatible 06 Oct 2018 U1 MIT No Details →
v3.46.2+incompatible 05 Oct 2018 U1 MIT No Details →
v3.46.1+incompatible 05 Oct 2018 U1 MIT No Details →
v3.45.1+incompatible 04 Oct 2018 U1 MIT No Details →
v3.37.6+incompatible 01 Sep 2018 U1 MIT No Details →
v3.37.5+incompatible 31 Aug 2018 U1 MIT No Details →
v3.37.4+incompatible 31 Aug 2018 U1 MIT No Details →
v3.37.3+incompatible 31 Aug 2018 U1 MIT No Details →
v3.37.2+incompatible 31 Aug 2018 U1 MIT No Details →
v3.37.1+incompatible 31 Aug 2018 U1 MIT No Details →
v3.33.1+incompatible 05 Aug 2018 U1 MIT No Details →
v3.32.2-0.20180729131006-3b0bfe9422c7+incompatible 29 Jul 2018 U1 MIT No Details →
v3.32.1+incompatible 29 Jul 2018 U1 MIT No Details →
v3.31.1+incompatible 21 Jul 2018 U1 MIT No Details →
v3.30.1+incompatible 17 Jul 2018 U1 MIT No Details →
v3.27.2-0.20180708210300-f8e6927581f9+incompatible 08 Jul 2018 U1 MIT No Details →
v3.27.2-0.20180708200826-bd4752a6ab9e+incompatible 08 Jul 2018 U1 MIT No Details →
v3.27.2-0.20180708190817-a8b0660df0b9+incompatible 08 Jul 2018 U1 MIT No Details →
v3.27.2-0.20180708102437-bbeae5be4856+incompatible 08 Jul 2018 U1 MIT No Details →
v3.27.2-0.20180702133023-6315217572a7+incompatible 02 Jul 2018 U1 MIT No Details →
v3.27.1+incompatible 01 Jul 2018 U1 MIT No Details →
v3.25.1+incompatible 09 Jun 2018 U1 MIT No Details →
v3.24.1+incompatible 04 Jun 2018 U1 MIT No Details →
v3.23.2+incompatible 28 May 2018 U1 MIT No Details →
v3.23.1+incompatible 27 May 2018 U1 MIT No Details →
v3.21.1+incompatible 11 May 2018 U1 MIT No Details →
v3.19.1+incompatible 20 Apr 2018 U1 MIT No Details →
v3.18.2+incompatible 18 Apr 2018 U1 MIT No Details →
v3.18.1+incompatible 14 Apr 2018 U1 MIT No Details →
v3.17.3+incompatible 13 Apr 2018 U1 MIT No Details →
v3.17.2+incompatible 13 Apr 2018 U1 MIT No Details →
v3.17.1+incompatible 13 Apr 2018 U1 MIT No Details →
v3.11.2+incompatible 04 Mar 2018 U1 MIT No Details →
v3.11.3+incompatible 04 Mar 2018 U1 MIT No Details →
v3.11.1+incompatible 02 Mar 2018 U1 MIT No Details →
v3.8.1+incompatible 12 Feb 2018 U1 MIT No Details →
v3.0.1+incompatible 01 Dec 2017 U1 MIT No Details →
v2.51.2+incompatible 26 Nov 2017 U1 MIT No Details →
v2.51.1+incompatible 25 Nov 2017 U1 MIT No Details →
v2.46.1+incompatible 08 Nov 2017 U1 MIT No Details →
v2.43.3+incompatible 26 Oct 2017 U1 MIT No Details →
v2.43.2+incompatible 24 Oct 2017 U1 MIT No Details →
v2.43.1+incompatible 24 Oct 2017 U1 MIT No Details →
v2.42.1+incompatible 24 Oct 2017 U1 MIT No Details →
v2.40.1+incompatible 13 Oct 2017 U1 MIT No Details →
v2.40.2+incompatible 13 Oct 2017 U1 MIT No Details →
v2.38.2+incompatible 27 Sep 2017 U1 MIT No Details →
v2.38.1+incompatible 27 Sep 2017 U1 MIT No Details →
v2.36.2+incompatible 27 Aug 2017 U1 MIT No Details →
v2.36.3+incompatible 27 Aug 2017 U1 MIT No Details →
v2.36.1+incompatible 25 Aug 2017 U1 MIT No Details →
v2.33.1+incompatible 09 Jun 2017 U1 MIT No Details →
v2.31.1+incompatible 04 Jun 2017 U1 MIT No Details →
v2.27.1+incompatible 15 May 2017 U1 MIT No Details →
v2.25.2+incompatible 02 May 2017 U1 MIT No Details →
v2.25.1+incompatible 28 Apr 2017 U1 MIT No Details →
v2.24.3+incompatible 25 Apr 2017 U1 MIT No Details →
v2.24.2+incompatible 24 Apr 2017 U1 MIT No Details →
v2.24.1+incompatible 23 Apr 2017 U1 MIT No Details →
v2.23.4+incompatible 20 Apr 2017 U1 MIT No Details →
v2.23.3+incompatible 19 Apr 2017 U1 MIT No Details →
v2.23.2+incompatible 18 Apr 2017 U1 MIT No Details →
v2.23.1+incompatible 18 Apr 2017 U1 MIT No Details →
v2.22.1+incompatible 13 Apr 2017 U1 MIT No Details →
v2.21.3+incompatible 05 Apr 2017 U1 MIT No Details →
v2.21.2+incompatible 04 Apr 2017 U1 MIT No Details →
v2.21.1+incompatible 03 Apr 2017 U1 MIT No Details →
v2.20.2+incompatible 02 Mar 2017 U1 MIT No Details →
v2.20.1+incompatible 26 Feb 2017 U1 MIT No Details →
v2.19.7+incompatible 23 Feb 2017 U1 MIT No Details →
v2.19.5+incompatible 23 Feb 2017 U1 MIT No Details →
v2.19.6+incompatible 23 Feb 2017 U1 MIT No Details →
v2.19.4+incompatible 23 Feb 2017 U1 — No Details →
v2.19.3+incompatible 23 Feb 2017 U1 — No Details →
v2.19.1+incompatible 23 Feb 2017 U1 — No Details →
v2.19.2+incompatible 23 Feb 2017 U1 — No Details →
v2.18.2+incompatible 17 Feb 2017 U1 — No Details →
v2.18.1+incompatible 14 Feb 2017 U1 — No Details →
v2.17.1+incompatible 04 Feb 2017 U1 — No Details →
v2.16.7+incompatible 31 Jan 2017 U1 — No Details →
v2.16.6+incompatible 29 Jan 2017 U1 — No Details →
v2.16.5+incompatible 29 Jan 2017 U1 — No Details →
v2.16.4+incompatible 28 Jan 2017 U1 — No Details →
v2.16.3+incompatible 28 Jan 2017 U1 — No Details →
v2.16.2+incompatible 28 Jan 2017 U1 — No Details →
v2.16.1+incompatible 27 Jan 2017 U1 — No Details →
v2.15.1+incompatible 16 Jan 2017 U1 — No Details →
v2.14.1+incompatible 10 Jan 2017 U1 — No Details →
v2.13.2+incompatible 04 Jan 2017 U1 — No Details →
v2.13.1+incompatible 02 Jan 2017 U1 — No Details →
v2.12.1+incompatible 26 Dec 2016 U1 — No Details →
v2.11.2+incompatible 21 Dec 2016 U1 — No Details →

The newest 120 of 181 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/v2fly/v2ray-core

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-4070: Off-by-one Error in v2fly/v2ray-core N/A unrated No fix published 21 Aug 2024

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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/v2fly/v2ray-core

Is github.com/v2fly/v2ray-core safe to use?

Vulert records 1 vulnerabilities for github.com/v2fly/v2ray-core in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/v2fly/v2ray-core's Vulert package health score?

Vulert scores github.com/v2fly/v2ray-core 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/v2fly/v2ray-core affected?

Yes. v4.15.0+incompatible, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does github.com/v2fly/v2ray-core have?

1 vulnerability is recorded for github.com/v2fly/v2ray-core in the Go ecosystem: 0 critical, 0 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/v2fly/v2ray-core vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/v2fly/v2ray-core in the last 12 months, and the oldest entry in this database dates to 21 Aug 2024. 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/v2fly/v2ray-core 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/v2fly/v2ray-core for upcoming vulnerabilities?

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