VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.mvel:mvel2: vulnerability history, versions and safety

org.mvel:mvel2 is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 100 releases, first recorded in Dec 2023. 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
1 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.mvel:mvel2 vulnerabilities

Vulert verdict on org.mvel:mvel2 2.6.0.Final i

Updated on 23 Oct 2026

Careful: 2.6.0.Final has 1 known vulnerability, and 1 has 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 Niche
  • Community Moderate

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 2.6.0.Final — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 27 Dec 2023 i
  • Highest CVSS 5.3 i
  • With no published fix 1 i
  • Depended on by 8 packages i
  • Stars 1,204 i
  • OpenSSF scorecard 5/10 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.mvel:mvel2, 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
2.6.0.Final 20 Oct 2026 M1 Apache-2.0 No Details →
2.5.4.Final 02 Sep 2026 M1 Apache-2.0 No Details →
2.5.3.Final 28 Aug 2026 M1 Apache-2.0 No Details →
2.5.2.Final 31 Jan 2024 M1 Apache-2.0 No Details →
2.5.1.Final 29 Nov 2023 M1 Apache-2.0 No Details →
2.5.0.Final 06 Jun 2023 M1 Apache-2.0 No Details →
2.4.15.Final 01 Mar 2023 M1 Apache-2.0 No Details →
2.4.14.Final 09 Dec 2021 M1 Apache-2.0 No Details →
2.4.13.Final 27 Sep 2021 M1 Apache-2.0 No Details →
2.4.12.Final 13 Jan 2021 M1 Apache-2.0 No Details →
2.4.11.Final 16 Dec 2020 M1 Apache-2.0 No Details →
2.4.10.Final 02 Sep 2020 M1 Apache-2.0 No Details →
2.4.9.Final 24 Aug 2020 M1 Apache-2.0 No Details →
2.4.8.Final 27 May 2020 M1 Apache-2.0 No Details →
2.4.7.Final 27 Feb 2020 M1 Apache-2.0 No Details →
2.4.5.Final 16 Dec 2019 M1 Apache-2.0 No Details →
2.4.4.Final 15 Feb 2019 M1 Apache-2.0 No Details →
2.4.3.Final 08 Nov 2018 M1 Apache-2.0 No Details →
2.4.2.Final 05 Sep 2018 M1 Apache-2.0 No Details →
2.4.1.Final 31 Aug 2018 M1 Apache-2.0 No Details →
2.4.0.Final 27 Oct 2017 M1 Apache-2.0 No Details →
2.3.2.Final 11 Sep 2017 M1 Apache-2.0 No Details →
2.3.1.Final 07 Sep 2016 M1 Apache-2.0 No Details →
2.3.0.Final 15 Jun 2016 M1 Apache-2.0 No Details →
2.2.8.Final 22 Mar 2016 M1 Apache-2.0 No Details →
2.2.7.Final 28 Sep 2015 M1 Apache-2.0 No Details →
2.2.6.Final 03 Aug 2015 M1 Apache-2.0 No Details →
2.2.5.Final 20 May 2015 M1 Apache-2.0 No Details →
2.2.4.Final 29 Jan 2015 M1 Apache-2.0 No Details →
2.2.3.Final 27 Jan 2015 M1 Apache-2.0 No Details →
2.2.2.Final 03 Oct 2014 M1 Apache-2.0 No Details →
2.2.1.Final 15 Jul 2014 M1 Apache-2.0 No Details →
2.2.0.Final 17 Apr 2014 M1 Apache-2.0 No Details →
2.1.9.Final 31 Jan 2014 M1 Apache-2.0 No Details →
2.1.8.Final 21 Nov 2013 M1 Apache-2.0 No Details →
2.1.7.Final 03 Oct 2013 M1 Apache-2.0 No Details →
2.1.6.Final 18 Jun 2013 M1 Apache-2.0 No Details →
2.1.5.Final 03 May 2013 M1 Apache-2.0 No Details →
2.1.4.Final 04 Feb 2013 M1 Apache-2.0 No Details →
2.1.3.Final 19 Sep 2012 M1 Apache-2.0 No Details →
2.1.2.Final 17 Sep 2012 M1 Apache-2.0 No Details →
2.1.1.Final 23 Aug 2012 M1 Apache-2.0 No Details →
2.1.0.Final 07 Aug 2012 M1 Apache-2.0 No Details →
2.1.0.drools16 04 May 2012 M1 Apache-2.0 No Details →
2.1.0.drools15 02 May 2012 M1 Apache-2.0 No Details →
2.1.0.drools14 19 Apr 2012 M1 Apache-2.0 No Details →
2.1.0.drools13 18 Apr 2012 M1 Apache-2.0 No Details →
2.1.0.drools12 16 Apr 2012 M1 Apache-2.0 No Details →
2.1.0.drools11 12 Apr 2012 M1 Apache-2.0 No Details →
2.1.0.drools10 16 Mar 2012 M1 Apache-2.0 No Details →
2.1.0.drools9 12 Mar 2012 M1 Apache-2.0 No Details →
2.1.0.drools8 23 Feb 2012 M1 Apache-2.0 No Details →
2.1.Beta8 02 Feb 2012 M1 Apache-2.0 No Details →
2.1.0.drools7 19 Jan 2012 M1 Apache-2.0 No Details →
2.1.0.drools6 18 Dec 2011 M1 Apache-2.0 No Details →
2.1.0.drools5 15 Dec 2011 M1 Apache-2.0 No Details →
2.1.Beta7 14 Nov 2011 M1 Apache-2.0 No Details →
2.1.0.drools4 19 Oct 2011 M1 Apache-2.0 No Details →
2.1.0.drools3 14 Oct 2011 M1 Apache-2.0 No Details →
2.1.Beta6 04 Aug 2011 M1 Apache-2.0 No Details →
2.1.Beta5 27 Jun 2011 M1 Apache-2.0 No Details →
2.1.0.drools2 22 Jun 2011 M1 Apache-2.0 No Details →
2.1.Beta4 21 Jun 2011 M1 Apache-2.0 No Details →
2.1.0.drools1 21 Jun 2011 M1 Apache-2.0 No Details →
2.1.Beta3 21 May 2011 M1 Apache-2.0 No Details →
2.1.beta2 17 Apr 2011 M1 — No Details →
2.1.Beta2 02 Mar 2011 M1 — No Details →
2.1.beta1 22 Feb 2011 M1 — No Details →
2.1.RC1 02 Feb 2011 M1 — No Details →
2.0.19 28 Oct 2010 M1 — No Details →
2.0.18-RC5 27 Aug 2010 M1 — No Details →
2.0.18-RC4 22 Aug 2010 M1 — No Details →
2.0.18-RC3 19 Aug 2010 M1 — No Details →
2.0.18-RC2 11 Aug 2010 M1 — No Details →
2.0.18-RC1 11 Aug 2010 M1 — No Details →
2.0.18 10 May 2010 M1 — No Details →
2.0.17 29 Mar 2010 M1 — No Details →
2.0.16 03 Feb 2010 M1 — No Details →
2.0.15 01 Dec 2009 M1 — No Details →
2.0.14 28 Oct 2009 M1 — No Details →
2.0.13 10 Aug 2009 M1 — No Details →
2.0.12 15 Jul 2009 M1 — No Details →
2.0.11 29 Jun 2009 M1 — No Details →
2.0.10 18 May 2009 M1 — No Details →
2.0.9 07 May 2009 M1 — No Details →
2.0.9pre2 17 Apr 2009 M1 — No Details →
2.0.9pre1 16 Apr 2009 M1 — No Details →
2.0.8 14 Apr 2009 M1 — No Details →
2.0.8pre1 09 Mar 2009 M1 — No Details →
2.0.7 03 Mar 2009 M1 — No Details →
2.0.6 12 Jan 2009 M1 — No Details →
2.0.5 27 Nov 2008 M1 — No Details →
2.0.4 21 Nov 2008 M1 — No Details →
2.0.3 18 Nov 2008 M1 — No Details →
2.0.2 10 Nov 2008 M1 — No Details →
2.0.1 03 Nov 2008 M1 — No Details →
2.0 24 Oct 2008 M1 — No Details →
2.0RC3 18 Oct 2008 M1 — No Details →
2.0RC2 17 Oct 2008 M1 — No Details →
2.0RC1 16 Oct 2008 M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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.mvel:mvel2

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-51079: mvel2 TimeOut error in ParseTools.subCompileExpression method 5.3 medium No fix published 27 Dec 2023

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.mvel:mvel2

Is org.mvel:mvel2 safe to use?

Vulert records 1 vulnerabilities for org.mvel:mvel2 in Maven: 0 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.mvel:mvel2's Vulert package health score?

Vulert scores org.mvel:mvel2 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.mvel:mvel2 affected?

Yes. 2.6.0.Final, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does org.mvel:mvel2 have?

1 vulnerability is recorded for org.mvel:mvel2 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.mvel:mvel2 vulnerabilities disclosed?

0 vulnerabilities were recorded for org.mvel:mvel2 in the last 12 months, and the oldest entry in this database dates to 27 Dec 2023. 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.mvel:mvel2 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.mvel:mvel2 for upcoming vulnerabilities?

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