VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jruby:jruby-parent: vulnerability history, versions and safety

org.jruby:jruby-parent is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 0 release, 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
1 vulnerabilities recorded M1
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.jruby:jruby-parent vulnerabilities

Vulert verdict on org.jruby:jruby-parent 9000.dev i

Updated on 23 Oct 2026

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

Package health score 66/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Moderate

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

  • Current release 9000.dev — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3,923 i
  • OpenSSF scorecard 4/10 i
  • Last release 152 months ago i
  • Licence GPL-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.jruby:jruby-parent, 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
10.0.7.0 21 Sep 2026 none GPL-2.0 — Details →
10.1.2.0 21 Sep 2026 none GPL-2.0 — Details →
10.1.1.0 22 Jul 2026 none GPL-2.0 — Details →
10.0.6.0 11 Jun 2026 none GPL-2.0 — Details →
9.4.15.0 08 Jun 2026 none GPL-2.0 — Details →
10.1.0.0 20 Apr 2026 none GPL-2.0 — Details →
10.0.5.0 06 Apr 2026 none GPL-2.0 — Details →
10.0.4.0 04 Mar 2026 none GPL-2.0 — Details →
10.0.3.0 02 Feb 2026 none GPL-2.0 — Details →
9.4.14.0 28 Aug 2025 none GPL-2.0 — Details →
10.0.2.0 07 Aug 2025 none GPL-2.0 — Details →
10.0.1.0 17 Jul 2025 none GPL-2.0 — Details →
9.4.13.0 10 Jun 2025 none GPL-2.0 — Details →
9.4.12.1 07 May 2025 none GPL-2.0 — Details →
10.0.0.1 07 May 2025 none GPL-2.0 — Details →
10.0.0.0 13 Apr 2025 none GPL-2.0 — Details →
9.4.12.0 11 Feb 2025 none GPL-2.0 — Details →
9.4.11.0 29 Jan 2025 none GPL-2.0 — Details →
9.4.10.0 20 Jan 2025 none GPL-2.0 — Details →
9.4.9.0 04 Nov 2024 none GPL-2.0 — Details →
9.4.8.0 02 Jul 2024 none GPL-2.0 — Details →
9.3.15.0 26 Jun 2024 none GPL-2.0 — Details →
9.4.7.0 29 Apr 2024 none GPL-2.0 — Details →
9.4.6.0 20 Feb 2024 none GPL-2.0 — Details →
9.3.14.0 20 Feb 2024 none GPL-2.0 — Details →
9.4.5.0 02 Nov 2023 none GPL-2.0 — Details →
9.3.13.0 02 Nov 2023 none GPL-2.0 — Details →
9.3.12.0 01 Nov 2023 none GPL-2.0 — Details →
9.4.4.0 18 Oct 2023 none GPL-2.0 — Details →
9.3.11.0 11 Sep 2023 none GPL-2.0 — Details →
9.4.3.0 07 Jun 2023 none GPL-2.0 — Details →
9.4.2.0 08 Mar 2023 none GPL-2.0 — Details →
9.4.1.0 07 Feb 2023 none GPL-2.0 — Details →
9.3.10.0 01 Feb 2023 none GPL-2.0 — Details →
9.4.0.0 23 Nov 2022 none GPL-2.0 — Details →
9.3.9.0 24 Oct 2022 none GPL-2.0 — Details →
9.3.8.0 13 Sep 2022 none GPL-2.0 — Details →
9.3.7.0 16 Aug 2022 none GPL-2.0 — Details →
9.3.6.0 27 Jun 2022 none GPL-2.0 — Details →
9.3.5.0 27 Jun 2022 none GPL-2.0 — Details →
9.2.21.0 27 Jun 2022 none GPL-2.0 — Details →
9.3.4.0 23 Mar 2022 none GPL-2.0 — Details →
9.3.3.0 19 Jan 2022 none GPL-2.0 — Details →
9.3.2.0 01 Dec 2021 none GPL-2.0 — Details →
9.2.20.1 30 Nov 2021 none GPL-2.0 — Details →
9.2.20.0 02 Nov 2021 none GPL-2.0 — Details →
9.3.1.0 13 Oct 2021 none GPL-2.0 — Details →
9.3.0.0 17 Sep 2021 none GPL-2.0 — Details →
9.2.19.0 15 Jun 2021 none GPL-2.0 — Details →
9.2.18.0 08 Jun 2021 none GPL-2.0 — Details →
9.2.17.0 29 Mar 2021 none GPL-2.0 — Details →
9.2.16.0 03 Mar 2021 none GPL-2.0 — Details →
9.2.15.0 24 Feb 2021 none GPL-2.0 — Details →
9.2.14.0 08 Dec 2020 none GPL-2.0 — Details →
9.2.13.0 03 Aug 2020 none GPL-2.0 — Details →
9.2.12.0 01 Jul 2020 none GPL-2.0 — Details →
9.2.11.1 25 Mar 2020 none GPL-2.0 — Details →
9.2.11.0 02 Mar 2020 none GPL-2.0 — Details →
9.2.10.0 18 Feb 2020 none GPL-2.0 — Details →
9.2.9.0 30 Oct 2019 none GPL-2.0 — Details →
9.2.8.0 12 Aug 2019 none GPL-2.0 — Details →
9.2.7.0 09 Apr 2019 none GPL-2.0 — Details →
9.2.6.0 11 Feb 2019 none GPL-2.0 — Details →
9.2.5.0 06 Dec 2018 none GPL-2.0 — Details →
9.2.4.1 28 Nov 2018 none GPL-2.0 — Details →
9.2.4.0 13 Nov 2018 none GPL-2.0 — Details →
9.2.3.0 09 Nov 2018 none GPL-2.0 — Details →
9.2.2.0 08 Nov 2018 none GPL-2.0 — Details →
9.2.1.0 06 Nov 2018 none GPL-2.0 — Details →
9.2.0.0 24 May 2018 none GPL-2.0 — Details →
9.1.17.0 20 Apr 2018 none GPL-2.0 — Details →
9.1.16.0 21 Feb 2018 none GPL-2.0 — Details →
9.1.15.0 07 Dec 2017 none GPL-2.0 — Details →
9.1.14.0 08 Nov 2017 none GPL-2.0 — Details →
9.1.13.0 06 Sep 2017 none GPL-2.0 — Details →
9.1.12.0 15 Jun 2017 none GPL-2.0 — Details →
9.1.11.0 14 Jun 2017 none GPL-2.0 — Details →
9.1.10.0 25 May 2017 none GPL-2.0 — Details →
9.1.9.0 15 May 2017 none GPL-2.0 — Details →
1.7.27 11 May 2017 none GPL-2.0 — Details →
9.1.8.0 06 Mar 2017 none GPL-2.0 — Details →
9.1.7.0 11 Jan 2017 none GPL-3.0 — Details →
9.1.6.0 09 Nov 2016 none GPL-3.0 — Details →
9.1.5.0 07 Sep 2016 none GPL-3.0 — Details →
9.1.4.0 01 Sep 2016 none GPL-3.0 — Details →
9.1.3.0 29 Aug 2016 none GPL-3.0 — Details →
1.7.26 26 Aug 2016 none GPL-3.0 — Details →
9.1.2.0 26 May 2016 none GPL-3.0 — Details →
9.1.1.0 19 May 2016 none GPL-3.0 — Details →
9.1.0.0 02 May 2016 none GPL-3.0 — Details →
1.7.25 13 Apr 2016 none GPL-3.0 — Details →
9.0.5.0 26 Jan 2016 none GPL-3.0 — Details →
1.7.24 20 Jan 2016 none GPL-3.0 — Details →
1.7.23 24 Nov 2015 none GPL-3.0 — Details →
9.0.4.0 12 Nov 2015 none GPL-3.0 — Details →
9.0.3.0 21 Oct 2015 none GPL-3.0 — Details →
9.0.2.0 19 Oct 2015 none GPL-3.0 — Details →
9.0.1.0 02 Sep 2015 none GPL-3.0 — Details →
1.7.22 20 Aug 2015 none GPL-3.0 — Details →
9.0.0.0 21 Jul 2015 none GPL-3.0 — Details →
9.0.0.0.rc2 09 Jul 2015 none — — Details →
1.7.21 07 Jul 2015 none — — Details →
9.0.0.0.rc1 10 Jun 2015 none — — Details →
1.7.20.1 10 Jun 2015 none — — Details →
1.7.20 04 May 2015 none — — Details →
9.0.0.0.pre2 28 Apr 2015 none — — Details →
1.7.19 30 Jan 2015 none — — Details →
9.0.0.0.pre1 20 Jan 2015 none — — Details →
1.7.18 22 Dec 2014 none — — Details →
1.7.17 09 Dec 2014 none — — Details →
1.7.16.2 08 Dec 2014 none — — Details →
1.7.16.1 28 Oct 2014 none — — Details →
1.7.16 25 Sep 2014 none — — Details →
1.7.15 03 Sep 2014 none — — Details →
1.7.14 27 Aug 2014 none — — Details →
1.7.13 24 Jun 2014 none — — Details →
1.7.12 15 Apr 2014 none — — Details →
1.7.11 24 Feb 2014 none — — Details →
9000.dev 20 Feb 2014 none — — Details →
1.7.10 09 Jan 2014 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 org.jruby:jruby-parent

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2012-5370: JRuby Denial of Service via Hash Collision N/A medium 1.7.1 17 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.jruby:jruby-parent

Is org.jruby:jruby-parent safe to use?

Vulert records 1 vulnerabilities for org.jruby:jruby-parent in Maven: 0 critical, 0 high, 1 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.jruby:jruby-parent's Vulert package health score?

Vulert scores org.jruby:jruby-parent 66/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).

Is the latest version of org.jruby:jruby-parent affected?

No. 9000.dev, 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.jruby:jruby-parent should I use?

9000.dev 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.jruby:jruby-parent have?

1 vulnerability is recorded for org.jruby:jruby-parent in the Maven ecosystem: 0 critical, 0 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.jruby:jruby-parent vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jruby:jruby-parent in the last 12 months, and the oldest entry in this database dates to 17 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.jruby:jruby-parent 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.jruby:jruby-parent for upcoming vulnerabilities?

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