VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

vantage6-node: vulnerability history, versions and safety

vantage6-node is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 0 release, from Oct 2023 to Jan 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded U3
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 vantage6-node vulnerabilities

Vulert verdict on vantage6-node 5.0.3 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 5.0.3 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 30 Jan 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 51 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, 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 vantage6-node, 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
4.15.2 22 Sep 2026 none — — Details →
5.0.3 21 Sep 2026 none MIT — Details →
5.0.3rc6 21 Sep 2026 none MIT — Details →
5.0.3rc5 21 Sep 2026 none MIT — Details →
4.15.2rc1 21 Sep 2026 none — — Details →
5.0.2 23 Jun 2026 none MIT — Details →
5.0.2rc2 22 Jun 2026 none MIT — Details →
5.0.1 05 Jun 2026 none MIT — Details →
5.0.1rc2 05 Jun 2026 none MIT — Details →
5.0.0 04 Jun 2026 none MIT — Details →
5.0.0rc91 02 Jun 2026 none MIT — Details →
5.0.0rc10 01 Jun 2026 none MIT — Details →
4.15.1 19 May 2026 none — — Details →
4.15.1rc1 19 May 2026 none — — Details →
5.0.0rc9 12 May 2026 none MIT — Details →
5.0.0rc8 12 May 2026 none MIT — Details →
5.0.0rc7 11 May 2026 none MIT — Details →
4.15.0 11 May 2026 none — — Details →
5.0.0rc6 11 May 2026 none MIT — Details →
4.15.0rc5 11 May 2026 none — — Details →
4.15.0rc4 08 May 2026 none — — Details →
5.0.0rc5 07 May 2026 none MIT — Details →
4.15.0rc3 04 May 2026 none — — Details →
5.0.0rc4 04 May 2026 none MIT — Details →
4.15.0rc2 24 Apr 2026 none — — Details →
4.15.0rc1 24 Apr 2026 none — — Details →
5.0.0rc2 30 Mar 2026 none MIT — Details →
5.0.0rc1 24 Mar 2026 none MIT — Details →
4.14.0 24 Mar 2026 none — — Details →
4.14.0rc1 24 Mar 2026 none — — Details →
5.0.0b4 09 Mar 2026 none MIT — Details →
4.13.7 16 Feb 2026 none — — Details →
4.13.7rc1 16 Feb 2026 none — — Details →
4.13.6 26 Jan 2026 none — — Details →
4.13.6rc3 26 Jan 2026 none — — Details →
5.0.0b2 22 Dec 2025 none MIT — Details →
4.13.5 19 Dec 2025 none — — Details →
4.13.4 11 Dec 2025 none — — Details →
4.13.4rc1 10 Dec 2025 none — — Details →
5.0.0b1 03 Dec 2025 none MIT — Details →
5.0.0a47 03 Dec 2025 none MIT — Details →
4.13.3 03 Dec 2025 none — — Details →
4.13.3rc2 03 Dec 2025 none — — Details →
4.13.3rc1 02 Dec 2025 none — — Details →
5.0.0a44 25 Nov 2025 none MIT — Details →
4.13.2 12 Nov 2025 none — — Details →
4.13.2rc1 12 Nov 2025 none — — Details →
5.0.0a43 30 Oct 2025 none MIT — Details →
5.0.0a42 28 Oct 2025 none MIT — Details →
5.0.0a41 27 Oct 2025 none MIT — Details →
5.0.0a40 23 Oct 2025 none MIT — Details →
5.0.0a38 17 Oct 2025 none MIT — Details →
5.0.0a37 14 Oct 2025 none MIT — Details →
4.13.1 07 Oct 2025 none — — Details →
4.13.0 29 Sep 2025 none — — Details →
4.13.0rc4 26 Sep 2025 none — — Details →
4.13.0rc3 25 Sep 2025 none — — Details →
4.13.0rc2 24 Sep 2025 none — — Details →
5.0.0a36 23 Sep 2025 none MIT — Details →
5.0.0a35 19 Sep 2025 none MIT — Details →
4.12.3rc1 17 Sep 2025 none — — Details →
5.0.0a34 28 Aug 2025 none MIT — Details →
4.12.2 19 Aug 2025 none — — Details →
4.12.2rc1 19 Aug 2025 none — — Details →
5.0.0a33 08 Aug 2025 none MIT — Details →
5.0.0a29 31 Jul 2025 none — — Details →
4.12.1 30 Jul 2025 none — — Details →
5.0.0a26 23 Jul 2025 none — — Details →
4.12.0 22 Jul 2025 none — — Details →
4.12.0rc2 22 Jul 2025 none — — Details →
5.0.0a22 30 Jun 2025 none — — Details →
5.0.0a21 27 Jun 2025 none — — Details →
5.0.0a20 25 Jun 2025 none — — Details →
5.0.0a19 20 Jun 2025 none — — Details →
5.0.0a18 17 Jun 2025 none — — Details →
4.11.0 12 Jun 2025 none — — Details →
4.11.0rc4 11 Jun 2025 none — — Details →
4.11.0rc3 11 Jun 2025 none — — Details →
4.11.0rc2 11 Jun 2025 none — — Details →
5.0.0a17 27 May 2025 none — — Details →
5.0.0a16 21 May 2025 none — — Details →
5.0.0a15 17 Apr 2025 none — — Details →
5.0.0a14 17 Apr 2025 none — — Details →
4.10.2 25 Mar 2025 none — — Details →
5.0.0a9 20 Mar 2025 none — — Details →
5.0.0a7 18 Mar 2025 none — — Details →
4.10.1 13 Mar 2025 none — — Details →
4.10.1rc1 12 Mar 2025 none — — Details →
4.10.0 07 Mar 2025 none — — Details →
4.10.0rc4 07 Mar 2025 none — — Details →
4.10.0rc3 03 Mar 2025 none — — Details →
4.10.0rc2 03 Mar 2025 none — — Details →
4.10.0rc1 26 Feb 2025 none — — Details →
4.9.1 23 Jan 2025 none — — Details →
4.9.0 15 Jan 2025 none — — Details →
4.9.0rc1 14 Jan 2025 none — — Details →
4.8.2 13 Dec 2024 none — — Details →
5.0.0a0 11 Dec 2024 none — — Details →
4.8.1 22 Nov 2024 none — — Details →
4.8.0 12 Nov 2024 none — — Details →
4.8.0rc3 12 Nov 2024 none — — Details →
4.8.0rc2 08 Nov 2024 none — — Details →
4.8.0rc1 08 Nov 2024 none — — Details →
4.7.1 01 Oct 2024 none — — Details →
4.7.1rc1 30 Sep 2024 none — — Details →
4.7.0 20 Aug 2024 none — — Details →
4.7.0rc2 14 Aug 2024 none — — Details →
4.7.0rc1 14 Aug 2024 none — — Details →
4.6.1 30 Jul 2024 none — — Details →
4.6.0 23 Jul 2024 none — — Details →
4.6.0rc7 22 Jul 2024 none — — Details →
4.6.0rc6 22 Jul 2024 none — — Details →
4.6.0rc5 17 Jul 2024 none — — Details →
4.6.0rc4 16 Jul 2024 none — — Details →
4.6.0rc3 16 Jul 2024 none — — Details →
4.5.5 13 Jun 2024 none — — Details →
4.5.4 13 Jun 2024 none — — Details →
4.5.3 06 Jun 2024 none — — Details →
4.5.2 03 Jun 2024 none — — Details →
4.5.1 03 Jun 2024 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for vantage6-node

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-21653: vantage6-node - Root Login with Password Authentication 9.8 critical 3fcc6e6a8bd1142fd7a558d8fdd2b246e55c8841 30 Jan 2024
CVE-2023-47631: Vulnerability in vantage6-node Allows Execution of Non-Whitelisted Algorithms 8.8 high bf83521eb12fa80aa5fc92ef1692010a9a7f8243 14 Nov 2023
Vulnerability in vantage6-node: Malicious User Access 5.4 medium 4.0.0 11 Oct 2023

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 vantage6-node

Is vantage6-node safe to use?

Vulert records 3 vulnerabilities for vantage6-node in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 3 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 vantage6-node's Vulert package health score?

Vulert scores vantage6-node 73/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 vantage6-node affected?

No. 5.0.3, 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 vantage6-node should I use?

5.0.3 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 vantage6-node have?

3 vulnerabilities are recorded for vantage6-node in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 3 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 vantage6-node vulnerabilities disclosed?

0 vulnerabilities were recorded for vantage6-node in the last 12 months, and the oldest entry in this database dates to 11 Oct 2023. 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 vantage6-node 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 vantage6-node for upcoming vulnerabilities?

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