Vulnerability Database · Maven · Package report

org.owasp.esapi:esapi: vulnerability history, versions and safety

org.owasp.esapi:esapi is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 25 releases, from Aug 2021 to Nov 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H2 M4 L1
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.

Vulert verdict on org.owasp.esapi:esapi 2.7.0.1-RC1 i

Updated on 23 Oct 2026

Good news: 2.7.0.1-RC1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 74/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 2.7.0.1-RC1 — unaffected i
  • Vulnerabilities on record 7 over 2 years · 0 in the last year i
  • Latest disclosure 27 Nov 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 650 i
  • OpenSSF scorecard 4/10 i
  • Last release 12 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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.owasp.esapi:esapi, 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.7.0.1-RC1 17 Oct 2025 none non-standard — Details →
2.7.0.0 27 Jun 2025 none non-standard — Details →
2.6.2.0 03 Jun 2025 none non-standard — Details →
2.6.1.0 19 May 2025 none non-standard — Details →
2.6.0.0 25 Nov 2024 none non-standard — Details →
2.5.5.0 08 Oct 2024 M1 non-standard Yes Details →
2.5.4.0 30 May 2024 M1 non-standard Yes Details →
2.5.3.1 01 Dec 2023 M1 non-standard Yes Details →
2.5.3.0 24 Nov 2023 M1 non-standard Yes Details →
2.5.2.0 13 Apr 2023 M1 non-standard Yes Details →
2.5.1.0 27 Nov 2022 H1 M1 non-standard Yes Details →
2.5.0.0 20 Jul 2022 H1 M1 non-standard Yes Details →
2.4.0.0 25 Apr 2022 H1 M1 non-standard Yes Details →
2.3.0.0 17 Apr 2022 H1 M1 non-standard Yes Details →
2.2.3.1 08 May 2021 H2 M2 non-standard Yes Details →
2.2.3.0 24 Mar 2021 H2 M2 non-standard Yes Details →
2.2.2.0 28 Nov 2020 H2 M2 non-standard Yes Details →
2.2.1.1 27 Jul 2020 H2 M2 non-standard Yes Details →
2.2.1.0 13 Jul 2020 H2 M2 non-standard Yes Details →
2.2.1.0-RC1 05 Jul 2020 H2 M2 non-standard Yes Details →
2.2.0.0 25 Jun 2019 H2 M2 non-standard Yes Details →
2.2.0.0-RC3 11 Jun 2019 H2 M2 non-standard Yes Details →
2.2.0.0-RC2 28 Apr 2019 H2 M2 non-standard Yes Details →
2.1.0.1 06 Feb 2016 H2 M2 non-standard Yes Details →
2.1.0 03 Sep 2013 H2 M3 non-standard Yes Details →
2.0.1 25 Jul 2011 H2 M3 L1 non-standard Yes Details →
2.0GA 11 May 2011 H2 M3 L1 non-standard Yes Details →
2.0_rc11 23 Mar 2011 H2 M3 L1 non-standard Yes Details →
2.0_rc10 18 Oct 2010 H2 M3 L1 non-standard Yes Details →
2.0_rc9 07 Sep 2010 H2 M3 L1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 4
  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.owasp.esapi:esapi

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →

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.owasp.esapi:esapi

Is org.owasp.esapi:esapi safe to use?

Vulert records 7 vulnerabilities for org.owasp.esapi:esapi in Maven: 0 critical, 2 high, 4 medium and 1 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.owasp.esapi:esapi's Vulert package health score?

Vulert scores org.owasp.esapi:esapi 74/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.owasp.esapi:esapi affected?

No. 2.7.0.1-RC1, 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.owasp.esapi:esapi should I use?

2.7.0.1-RC1 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.owasp.esapi:esapi have?

7 vulnerabilities are recorded for org.owasp.esapi:esapi in the Maven ecosystem: 0 critical, 2 high, 4 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.owasp.esapi:esapi vulnerabilities disclosed?

0 vulnerabilities were recorded for org.owasp.esapi:esapi in the last 12 months, and the oldest entry in this database dates to 13 Aug 2021. 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.owasp.esapi:esapi 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.owasp.esapi:esapi for upcoming vulnerabilities?

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