VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

org.jenkins-ci.plugins:ssh is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 9 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 H2 M1
i
3 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 org.jenkins-ci.plugins:ssh vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:ssh 159.v496ca_25e5e82 i

Updated on 23 Oct 2026

Careful: 159.v496ca_25e5e82 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

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 159.v496ca_25e5e82 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 18 May 2022 i
  • Highest CVSS 7.1 i
  • With no published fix 3 i
  • Stars 55 i
  • Last release 2 months ago 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:ssh, 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
159.v496ca_25e5e82 17 Aug 2026 H2 M1 — No Details →
158.ve2a_e90fb_7319 18 Nov 2024 H2 M1 — No Details →
2.9 14 Nov 2024 H2 M1 — No Details →
2.8 13 Nov 2024 H2 M1 — No Details →
2.7 11 Nov 2024 H2 M1 — No Details →
2.6.1 13 Apr 2018 H2 M1 — No Details →
2.6 07 Apr 2018 H2 M1 — No Details →
2.5 07 Jul 2017 H2 M1 — No Details →
2.4 08 Jan 2014 H2 M1 — No Details →

All 9 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:ssh

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-30959: Missing Authorization in Jenkins SSH plugin 7.1 high No fix published 18 May 2022
CVE-2022-30958: Cross Site Request Forgery in Jenkins SSH Plugin 7.1 high No fix published 18 May 2022
CVE-2022-30957: Missing permission check in Jenkins SSH Plugin 4.3 medium No fix published 18 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:ssh

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

Vulert records 3 vulnerabilities for org.jenkins-ci.plugins:ssh in Maven: 0 critical, 2 high, 1 medium and 0 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is org.jenkins-ci.plugins:ssh's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:ssh 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 org.jenkins-ci.plugins:ssh affected?

Yes. 159.v496ca_25e5e82, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of org.jenkins-ci.plugins:ssh should I use?

159.v496ca_25e5e82 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:ssh have?

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

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

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