VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:vsphere-cloud: vulnerability history, versions and safety

org.jenkins-ci.plugins:vsphere-cloud is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 36 releases, first recorded in May 2022. 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 H1 M2
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 org.jenkins-ci.plugins:vsphere-cloud vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:vsphere-cloud 5.706.v891625470e78 i

Updated on 23 Oct 2026

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

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

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

  • Current release 5.706.v891625470e78 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 52 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, 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 org.jenkins-ci.plugins:vsphere-cloud, 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
5.706.v891625470e78 09 Oct 2026 none Apache-2.0 — Details →
5.703.v08b_28e1165e0 09 Oct 2026 none Apache-2.0 — Details →
5.692.v8c617b_d8b_f92 04 Oct 2026 none Apache-2.0 — Details →
5.688.v5cd5d96810dc 04 Oct 2026 none Apache-2.0 — Details →
5.684.v548527e4455b_ 03 Oct 2026 none Apache-2.0 — Details →
5.682.vfcd36e5459b_c 03 Oct 2026 none Apache-2.0 — Details →
5.674.ve9f11672e2f0 03 Oct 2026 none Apache-2.0 — Details →
5.659.vcecc71c116a_e 01 Oct 2026 none Apache-2.0 — Details →
5.656.vb_34fceb_455c6 01 Oct 2026 none Apache-2.0 — Details →
4.655.v81a_d468efa_0f 30 Sep 2026 none Apache-2.0 — Details →
4.654.vfb_78ec86d306 30 Sep 2026 none Apache-2.0 — Details →
4.651.vb_5699c81ca_79 30 Sep 2026 none Apache-2.0 — Details →
4.649.v8b_c9057d5748 30 Sep 2026 none Apache-2.0 — Details →
4.646.va_280eb_27a_926 30 Sep 2026 none Apache-2.0 — Details →
4.633.v1122cc726568 30 Sep 2026 none Apache-2.0 — Details →
4.625.v30e4317804d3 30 Sep 2026 none Apache-2.0 — Details →
4.619.v947456a_189b_7 30 Sep 2026 none Apache-2.0 — Details →
4.604.v8d1097b_6767f 30 Sep 2026 none Apache-2.0 — Details →
4.592.v7b_93a_6a_3ff33 30 Sep 2026 none Apache-2.0 — Details →
4.573.v2a_8a_a_1871263 01 Sep 2026 none Apache-2.0 — Details →
4.563.v2d59e5e96653 13 Aug 2026 none Apache-2.0 — Details →
4.556.v88a_c5a_0f8a_1d 05 Aug 2026 none Apache-2.0 — Details →
4.554.va_e21a_3cd25ea_ 29 Jul 2026 none Apache-2.0 — Details →
4.547.v9d4a_e5696e9a_ 29 Jul 2026 none Apache-2.0 — Details →
4.545.v3805b_61b_67e8 22 Jul 2026 none Apache-2.0 — Details →
4.530.v1b_68fb_22777c 29 Jun 2026 none Apache-2.0 — Details →
3.521.v564a_a_f82677b_ 29 Jun 2026 none Apache-2.0 — Details →
3.512.vfb_0824b_5068c 12 Mar 2026 none Apache-2.0 — Details →
3.510.v94a_44f56b_332 11 Mar 2026 none Apache-2.0 — Details →
2.28 11 Mar 2026 none Apache-2.0 — Details →
2.10 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.11 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.4 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.6 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.23 13 Feb 2024 none Apache-2.0 — Details →
0.4 13 Feb 2024 H1 M2 — Yes Details →
2.20 13 Feb 2024 none Apache-2.0 — Details →
1.1.1 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.0.2 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.6 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.5 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.5 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
0.10 13 Feb 2024 H1 M2 — Yes Details →
2.1 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.27 13 Feb 2024 none Apache-2.0 — Details →
0.5 13 Feb 2024 H1 M2 — Yes Details →
1.0.1 13 Feb 2024 H1 M2 — Yes Details →
2.19 13 Feb 2024 none Apache-2.0 — Details →
2.24 13 Feb 2024 none Apache-2.0 — Details →
2.15 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.11 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.17 13 Feb 2024 none Apache-2.0 — Details →
2.21 13 Feb 2024 none Apache-2.0 — Details →
1.1.10 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.13 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.26 13 Feb 2024 none Apache-2.0 — Details →
2.14 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.3 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.2 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.25 13 Feb 2024 none Apache-2.0 — Details →
2.18 13 Feb 2024 none Apache-2.0 — Details →
2.16 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.8 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.7 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.12 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
0.7 13 Feb 2024 H1 M2 — Yes Details →
1.1.0 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.9 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.2 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.9 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.3 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
2.4 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
0.9 13 Feb 2024 H1 M2 — Yes Details →
2.22 13 Feb 2024 none Apache-2.0 — Details →
2.0 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
1.1.12 13 Feb 2024 H1 M2 Apache-2.0 Yes Details →
0.8 13 Feb 2024 H1 M2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3

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 org.jenkins-ci.plugins:vsphere-cloud

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1000153: Jenkins vSphere Plugin Cross-Site Request Forgery vulnerability in org.jenkins-ci.plugins:vsphere-cloud 8.8 high 2.17 14 May 2022
CVE-2018-1000152: Jenkins vSphere Plugin incorrect authorization vulnerability 6.3 medium 2.17 13 May 2022
CVE-2018-1000151: Jenkins vSphere Plugin SSL/TLS Certificate Validation Bypass 5.6 medium 2.17 14 May 2022

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 org.jenkins-ci.plugins:vsphere-cloud

Is org.jenkins-ci.plugins:vsphere-cloud safe to use?

Vulert records 3 vulnerabilities for org.jenkins-ci.plugins:vsphere-cloud in Maven: 0 critical, 1 high, 2 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 org.jenkins-ci.plugins:vsphere-cloud's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:vsphere-cloud 78/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 org.jenkins-ci.plugins:vsphere-cloud affected?

No. 5.706.v891625470e78, 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 org.jenkins-ci.plugins:vsphere-cloud should I use?

5.706.v891625470e78 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 org.jenkins-ci.plugins:vsphere-cloud have?

3 vulnerabilities are recorded for org.jenkins-ci.plugins:vsphere-cloud in the Maven ecosystem: 0 critical, 1 high, 2 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 org.jenkins-ci.plugins:vsphere-cloud vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jenkins-ci.plugins:vsphere-cloud in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 org.jenkins-ci.plugins:vsphere-cloud 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 org.jenkins-ci.plugins:vsphere-cloud for upcoming vulnerabilities?

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