VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.mchange:mchange-commons-java: vulnerability history, versions and safety

com.mchange:mchange-commons-java is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 33 releases, from Feb 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 14 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.mchange:mchange-commons-java vulnerabilities

Vulert verdict on com.mchange:mchange-commons-java 0.6.1 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

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

  • Current release 0.6.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 14 Aug 2026 i
  • Highest CVSS 8.9 i
  • With no published fix 0 i
  • Depended on by 96 packages i
  • Last release 4 months ago i
  • Licence LGPL-2.1 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 com.mchange:mchange-commons-java, 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
0.6.1 08 Jun 2026 none LGPL-2.1 — Details →
0.6.0 03 Jun 2026 none LGPL-2.1 — Details →
0.5.0 23 Apr 2026 H1 LGPL-2.1 Yes Details →
0.4.0 21 Feb 2026 H1 LGPL-2.1 Yes Details →
0.3.2 12 Feb 2025 H2 LGPL-2.1 Yes Details →
0.3.1 05 May 2024 H2 LGPL-2.1 Yes Details →
0.3.0 23 Feb 2024 H2 LGPL-2.1 Yes Details →
0.2.20 19 Jan 2020 H2 LGPL-2.1 Yes Details →
0.2.19 09 Nov 2019 H2 LGPL-2.1 Yes Details →
0.2.18 12 Oct 2019 H2 LGPL-2.1 Yes Details →
0.2.17 11 Oct 2019 H2 LGPL-2.1 Yes Details →
0.2.16 30 Jun 2019 H2 LGPL-2.1 Yes Details →
0.2.15 02 Feb 2018 H2 LGPL-2.1 Yes Details →
0.2.14 07 Nov 2017 H2 LGPL-2.1 Yes Details →
0.2.13 07 Nov 2017 H2 LGPL-2.1 Yes Details →
0.2.12 06 May 2016 H2 LGPL-2.1 Yes Details →
0.2.11 09 Dec 2015 H2 LGPL-2.1 Yes Details →
0.2.10 30 May 2015 H2 LGPL-2.1 Yes Details →
0.2.9 02 Jan 2015 H2 LGPL-2.1 Yes Details →
0.2.8 08 Oct 2014 H2 LGPL-2.1 Yes Details →
0.2.7 04 Apr 2014 H2 LGPL-2.1 Yes Details →
0.2.6.5 23 Mar 2014 H2 LGPL-2.1 Yes Details →
0.2.6.3 07 Dec 2013 H2 LGPL-2.1 Yes Details →
0.2.6.2 23 Oct 2013 H2 LGPL-2.1 Yes Details →
0.2.6.1 23 Aug 2013 H2 LGPL-2.1 Yes Details →
0.2.6 22 May 2013 H2 LGPL-2.1 Yes Details →
0.2.5 23 Apr 2013 H2 LGPL-2.1 Yes Details →
0.2.4 20 Mar 2013 H2 LGPL-2.1 Yes Details →
0.2.3.4 20 Mar 2013 H2 LGPL-2.1 Yes Details →
0.2.3.3 19 Dec 2012 H2 LGPL-2.1 Yes Details →
0.2.3.2 13 Dec 2012 H2 LGPL-2.1 Yes Details →
0.2.3.1 22 Nov 2012 H2 LGPL-2.1 Yes Details →
0.2.3 29 Sep 2012 H2 LGPL-2.1 Yes Details →
0.2.2 16 Jun 2012 H2 LGPL-2.1 Yes Details →
0.2.1-RELEASE 18 May 2012 H2 LGPL-2.1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for com.mchange:mchange-commons-java

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27727: mchange-commons-java Remote Code Execution Vulnerability 8.9 high 0.4.0 25 Feb 2026
CVE-2026-55153: mchange-commons-java JNDI Injection and Deserialization Vulnerability 7.1 high 0.6.0 14 Aug 2026

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 com.mchange:mchange-commons-java

Is com.mchange:mchange-commons-java safe to use?

Vulert records 2 vulnerabilities for com.mchange:mchange-commons-java in Maven: 0 critical, 2 high, 0 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 com.mchange:mchange-commons-java's Vulert package health score?

Vulert scores com.mchange:mchange-commons-java 77/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 com.mchange:mchange-commons-java affected?

No. 0.6.1, 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 com.mchange:mchange-commons-java should I use?

0.6.1 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 com.mchange:mchange-commons-java have?

2 vulnerabilities are recorded for com.mchange:mchange-commons-java in the Maven ecosystem: 0 critical, 2 high, 0 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 com.mchange:mchange-commons-java vulnerabilities disclosed?

2 vulnerabilities were recorded for com.mchange:mchange-commons-java in the last 12 months, and the oldest entry in this database dates to 25 Feb 2026. 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 com.mchange:mchange-commons-java 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 com.mchange:mchange-commons-java for upcoming vulnerabilities?

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