VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

org.jenkins-ci.plugins:subversion is a package in the Maven ecosystem. Vulert records 8 vulnerabilities for it across 81 releases, from Apr 2022 to 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
8 vulnerabilities recorded M8
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:subversion vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:subversion 1327.vc36e0019a_653 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 1327.vc36e0019a_653 — unaffected i
  • Vulnerabilities on record 8 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 130 i
  • Last release 1 month ago i
  • Licence MIT 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:subversion, 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
1327.vc36e0019a_653 05 Sep 2026 none MIT — Details →
1303.vcfd9679fb_c12 29 Dec 2025 none MIT — Details →
1292.ve8cf25770ee3 11 Aug 2025 none MIT — Details →
1287.vd2d507146906 06 Feb 2025 none MIT — Details →
1283.vfc8b_92d49a_06 22 Jan 2025 none MIT — Details →
1281.vc8837f91a_07a_ 05 Nov 2024 none MIT — Details →
1280.v5465ce107f22 29 Oct 2024 none MIT — Details →
1278.vb_8220b_249cf5 17 Oct 2024 none MIT — Details →
1275.va_7b_014f3fc2c 16 Aug 2024 none MIT — Details →
1268.v0581f58a_b_3cd 24 Jun 2024 none MIT — Details →
1269.v53185011cd9f 24 Jun 2024 none MIT — Details →
1265.v4b_6d7cd94421 24 Jun 2024 none MIT — Details →
1261.v040121d29c7c 21 Jun 2024 none MIT — Details →
1256.vee91953217b_6 26 Mar 2024 none MIT — Details →
2.13.1 13 Feb 2024 M4 MIT Yes Details →
2.0-alpha-1 13 Feb 2024 M7 MIT Yes Details →
2.14.3 13 Feb 2024 M3 MIT Yes Details →
1.42 13 Feb 2024 M8 MIT Yes Details →
2.13.0 13 Feb 2024 M5 MIT Yes Details →
1.53 13 Feb 2024 M8 MIT Yes Details →
2.5-beta-2 13 Feb 2024 M7 MIT Yes Details →
2.12.0 13 Feb 2024 M5 MIT Yes Details →
2.7.1.1 13 Feb 2024 M7 MIT Yes Details →
2.17.2 13 Feb 2024 none MIT — Details →
2.13.2 13 Feb 2024 M3 MIT Yes Details →
2.14.4 13 Feb 2024 M3 MIT Yes Details →
1.36 13 Feb 2024 M8 MIT Yes Details →
1.43 13 Feb 2024 M8 MIT Yes Details →
2.5.2 13 Feb 2024 M7 MIT Yes Details →
1.38 13 Feb 2024 M8 MIT Yes Details →
2.4.5 13 Feb 2024 M7 MIT Yes Details →
1.48 13 Feb 2024 M8 MIT Yes Details →
1.51 13 Feb 2024 M8 MIT Yes Details →
2.10.6 13 Feb 2024 M5 MIT Yes Details →
2.4.4 13 Feb 2024 M7 MIT Yes Details →
2.5-beta-4 13 Feb 2024 M7 MIT Yes Details →
1.26 13 Feb 2024 M8 MIT Yes Details →
2.3 13 Feb 2024 M7 MIT Yes Details →
2.1 13 Feb 2024 M7 MIT Yes Details →
2.10.3 13 Feb 2024 M5 MIT Yes Details →
2.10.4 13 Feb 2024 M5 MIT Yes Details →
2.11.0 13 Feb 2024 M5 MIT Yes Details →
2.14.5 13 Feb 2024 M3 MIT Yes Details →
2.15.0 13 Feb 2024 M3 MIT Yes Details →
2.17.0 13 Feb 2024 none MIT — Details →
1.29 13 Feb 2024 M8 MIT Yes Details →
1.35 13 Feb 2024 M8 MIT Yes Details →
2.8 13 Feb 2024 M7 MIT Yes Details →
2.4 13 Feb 2024 M7 MIT Yes Details →
2.5.7 13 Feb 2024 M7 MIT Yes Details →
2.5.4 13 Feb 2024 M7 MIT Yes Details →
2.9 13 Feb 2024 M6 MIT Yes Details →
2.5 13 Feb 2024 M7 MIT Yes Details →
2.10.1 13 Feb 2024 M6 MIT Yes Details →
2.16.0 13 Feb 2024 none MIT — Details →
2.5-beta-1 13 Feb 2024 M7 MIT Yes Details →
1.30 13 Feb 2024 M8 MIT Yes Details →
1.45 13 Feb 2024 M8 MIT Yes Details →
1.31 13 Feb 2024 M8 MIT Yes Details →
1.54 13 Feb 2024 M7 MIT Yes Details →
2.5.6 13 Feb 2024 M7 MIT Yes Details →
1.34 13 Feb 2024 M8 MIT Yes Details →
2.17.3 13 Feb 2024 none MIT — Details →
1.39 13 Feb 2024 M8 MIT Yes Details →
2.2 13 Feb 2024 M7 MIT Yes Details →
1.40 13 Feb 2024 M8 MIT Yes Details →
2.4.1 13 Feb 2024 M7 MIT Yes Details →
2.10.5 13 Feb 2024 M5 MIT Yes Details →
2.4.2 13 Feb 2024 M7 MIT Yes Details →
2.15.2 13 Feb 2024 M2 MIT Yes Details →
2.5.1 13 Feb 2024 M7 MIT Yes Details →
2.12.2 13 Feb 2024 M5 MIT Yes Details →
2.14.1 13 Feb 2024 M3 MIT Yes Details →
2.5.3 13 Feb 2024 M7 MIT Yes Details →
2.10.2 13 Feb 2024 M6 MIT Yes Details →
2.11.1 13 Feb 2024 M5 MIT Yes Details →
2.7.2 13 Feb 2024 M7 MIT Yes Details →
1.33 13 Feb 2024 M8 MIT Yes Details →
2.6 13 Feb 2024 M7 MIT Yes Details →
2.0 13 Feb 2024 M7 MIT Yes Details →
2.14.0 13 Feb 2024 M3 MIT Yes Details →
2.10 13 Feb 2024 M6 MIT Yes Details →
2.15.3 13 Feb 2024 M2 MIT Yes Details →
2.4.3 13 Feb 2024 M7 MIT Yes Details →
1.37 13 Feb 2024 M8 MIT Yes Details →
1.28 13 Feb 2024 M8 MIT Yes Details →
2.5.5 13 Feb 2024 M7 MIT Yes Details →
2.14.2 13 Feb 2024 M3 MIT Yes Details →
1.50 13 Feb 2024 M8 MIT Yes Details →
1.25 13 Feb 2024 M8 MIT Yes Details →
2.5-beta-3 13 Feb 2024 M7 MIT Yes Details →
2.0-beta-1 13 Feb 2024 M7 MIT Yes Details →
2.12.1 13 Feb 2024 M5 MIT Yes Details →
1.24 13 Feb 2024 M8 MIT Yes Details →
2.15.5 13 Feb 2024 none MIT — Details →
1.41 13 Feb 2024 M8 MIT Yes Details →
2.15.4 13 Feb 2024 none MIT — Details →
2.17.1 13 Feb 2024 none MIT — Details →
2.7.1 13 Feb 2024 M7 MIT Yes Details →
2.15.1 13 Feb 2024 M2 MIT Yes Details →
1.32 13 Feb 2024 M8 — Yes Details →
1.44 13 Feb 2024 M8 — Yes Details →

All 102 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 8

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

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:subversion

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000085: Jenkins Subversion Plugin Cross-Site Request Forgery vulnerability 6.5 medium 2.9 17 May 2022
CVE-2021-21698: Path traversal vulnerability in Jenkins Subversion Plugin allows reading arbitrary files 6.5 medium 2.15.1 24 May 2022
CVE-2020-2304: XXE vulnerability in Jenkins Subversion Plugin 6.5 medium 2.13.2 24 May 2022
CVE-2020-2111: Subversion Plugin stored XSS vulnerability before v2.13.1 5.4 medium 2.13.1 24 May 2022
CVE-2022-29046: Stored Cross-site Scripting vulnerability in Jenkins Subversion Plugin 5.4 medium 2.15.4 13 Apr 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:subversion

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

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

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

No. 1327.vc36e0019a_653, 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:subversion should I use?

1327.vc36e0019a_653 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:subversion have?

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

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

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