VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

vproxy: vulnerability history, versions and safety

vproxy is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 36 releases, first recorded in Jul 2025. 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 H1
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 vproxy vulnerabilities

Vulert verdict on vproxy 2.5.5 i

Updated on 23 Oct 2026

Good news: 2.5.5, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

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

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

  • Current release 2.5.5 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 30 Jul 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 129 i
  • Last release 11 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by crates.io, 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 vproxy, 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
2.5.5 16 Nov 2025 none GPL-3.0 — Details →
2.5.3 30 Oct 2025 none GPL-3.0 — Details →
2.5.2 04 Oct 2025 none GPL-3.0 — Details →
2.5.1 02 Oct 2025 none GPL-3.0 — Details →
2.5.0 01 Oct 2025 none GPL-3.0 — Details →
2.4.4 27 Sep 2025 none GPL-3.0 — Details →
2.4.3 26 Sep 2025 none GPL-3.0 — Details →
2.4.5 25 Sep 2025 none GPL-3.0 — Details →
2.4.2 25 Sep 2025 none GPL-3.0 — Details →
2.4.1 24 Sep 2025 none GPL-3.0 — Details →
2.4.0 30 Jul 2025 none GPL-3.0 — Details →
2.3.3 27 Jul 2025 H1 GPL-3.0 Yes Details →
2.3.2 05 Jul 2025 H1 GPL-3.0 Yes Details →
2.3.1 10 Jun 2025 H1 GPL-3.0 Yes Details →
2.3.0 22 Apr 2025 H1 GPL-3.0 Yes Details →
2.0.77 19 Mar 2025 H1 GPL-3.0 Yes Details →
2.0.65 06 Mar 2025 H1 GPL-3.0 Yes Details →
2.0.60 15 Feb 2025 H1 GPL-3.0 Yes Details →
2.0.55 01 Feb 2025 H1 GPL-3.0 Yes Details →
2.0.51 31 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.50 24 Jan 2025 H1 GPL-3.0 Yes Details →
2.2.0 24 Jan 2025 H1 GPL-3.0 Yes Details →
2.1.0 24 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.26 21 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.25 20 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.12 19 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.11 19 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.10 18 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.6 18 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.5 18 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.1 18 Jan 2025 H1 GPL-3.0 Yes Details →
2.0.0 17 Jan 2025 H1 MIT Yes Details →
1.3.2 16 Jan 2025 H1 MIT Yes Details →
1.3.1 16 Jan 2025 H1 MIT Yes Details →
1.3.0 10 Dec 2024 H1 MIT Yes Details →
1.2.6 12 Oct 2024 H1 MIT Yes Details →
1.2.5 07 Sep 2024 H1 MIT Yes Details →
1.2.4 17 Aug 2024 H1 MIT Yes Details →
1.2.3 22 Jul 2024 H1 MIT Yes Details →
1.2.1 14 Jul 2024 H1 MIT Yes Details →
1.1.2 07 Jul 2024 H1 MIT Yes Details →
1.1.1 07 Jul 2024 H1 MIT Yes Details →
1.0.0 04 Jun 2024 H1 MIT Yes Details →
0.3.7 26 May 2024 H1 MIT Yes Details →
0.3.2 16 May 2024 H1 MIT Yes Details →
0.2.2 11 May 2024 H1 MIT Yes Details →
0.2.1 03 May 2024 H1 MIT Yes Details →

All 47 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 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 vproxy

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-54581: vproxy Divide by Zero DoS Vulnerability 7.5 high 2.4.0 30 Jul 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 vproxy

Is vproxy safe to use?

Vulert records 1 vulnerabilities for vproxy in crates.io: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is vproxy's Vulert package health score?

Vulert scores vproxy 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 vproxy affected?

No. 2.5.5, 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 vproxy should I use?

2.5.5 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 vproxy have?

1 vulnerability is recorded for vproxy in the crates.io ecosystem: 0 critical, 1 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 vproxy vulnerabilities disclosed?

0 vulnerabilities were recorded for vproxy in the last 12 months, and the oldest entry in this database dates to 30 Jul 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 vproxy 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 vproxy for upcoming vulnerabilities?

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