Vulnerability Database · Maven · Package report
javax.validation:validation-api: vulnerability history, versions and safety
javax.validation:validation-api is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Maven ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on javax.validation:validation-api 2.0.1.Final i
Updated on 23 Oct 2026
Good news: 2.0.1.Final, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on 2.0.1.Final or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.1.Final too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.0.1.Final — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 21,009 packages i
- Stars 165 i
- OpenSSF scorecard 5/10 i
- Last release 106 months ago 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 javax.validation:validation-api, 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.
- 2.0.1.Final 19 Dec 2017
- 2.0.0.Final 03 Aug 2017
- 2.0.0.CR3 11 Jul 2017
- 2.0.0.CR2 05 Jul 2017
- 2.0.0.CR1 21 Jun 2017
- 2.0.0.Beta2 17 May 2017
- 2.0.0.Beta1 24 Apr 2017
- 2.0.0.Alpha2 28 Mar 2017
- 2.0.0.Alpha1 03 Feb 2017
- 1.1.0.Final 10 Apr 2013
- 1.1.0.CR3 20 Mar 2013
- 1.1.0.CR2 14 Mar 2013
- 1.1.0.CR1 20 Feb 2013
- 1.1.0.Beta4 15 Feb 2013
- 1.1.0.Beta3 01 Feb 2013
- 1.1.0.Beta2 27 Nov 2012
- 1.1.0.Beta1 19 Oct 2012
- 1.1.0.Alpha1 14 Mar 2012
- 1.0.0.GA 08 Oct 2009
- 1.0.CR5 27 Aug 2009
- 1.0.CR4 13 Aug 2009
- 1.0.CR3 08 Jul 2009
- 1.0.CR2 27 Apr 2009
- 1.0.CR1 18 Mar 2009
- 1.0.Beta4 03 Mar 2009
- 1.0.Beta3 11 Feb 2009
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 2.0.1.Final | 19 Dec 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.Final | 03 Aug 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.CR3 | 11 Jul 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.CR2 | 05 Jul 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.CR1 | 21 Jun 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.Beta2 | 17 May 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.Beta1 | 24 Apr 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.Alpha2 | 28 Mar 2017 | none | Apache-2.0 | — | Details → |
| 2.0.0.Alpha1 | 03 Feb 2017 | none | Apache-2.0 | — | Details → |
| 1.1.0.Final | 10 Apr 2013 | none | Apache-2.0 | — | Details → |
| 1.1.0.CR3 | 20 Mar 2013 | none | Apache-2.0 | — | Details → |
| 1.1.0.CR2 | 14 Mar 2013 | none | Apache-2.0 | — | Details → |
| 1.1.0.CR1 | 20 Feb 2013 | none | Apache-2.0 | — | Details → |
| 1.1.0.Beta4 | 15 Feb 2013 | none | Apache-2.0 | — | Details → |
| 1.1.0.Beta3 | 01 Feb 2013 | none | Apache-2.0 | — | Details → |
| 1.1.0.Beta2 | 27 Nov 2012 | none | Apache-2.0 | — | Details → |
| 1.1.0.Beta1 | 19 Oct 2012 | none | Apache-2.0 | — | Details → |
| 1.1.0.Alpha1 | 14 Mar 2012 | none | Apache-2.0 | — | Details → |
| 1.0.0.GA | 08 Oct 2009 | none | Apache-2.0 | — | Details → |
| 1.0.CR5 | 27 Aug 2009 | none | Apache-2.0 | — | Details → |
| 1.0.CR4 | 13 Aug 2009 | none | Apache-2.0 | — | Details → |
| 1.0.CR3 | 08 Jul 2009 | none | Apache-2.0 | — | Details → |
| 1.0.CR2 | 27 Apr 2009 | none | Apache-2.0 | — | Details → |
| 1.0.CR1 | 18 Mar 2009 | none | Apache-2.0 | — | Details → |
| 1.0.Beta4 | 03 Mar 2009 | none | Apache-2.0 | — | Details → |
| 1.0.Beta3 | 11 Feb 2009 | none | Apache-2.0 | — | Details → |
All 26 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for javax.validation:validation-api
No vulnerabilities match this view.
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
Questions
About javax.validation:validation-api
Is javax.validation:validation-api safe to use?
Vulert has no vulnerabilities on record for javax.validation:validation-api in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is javax.validation:validation-api's Vulert package health score?
Vulert scores javax.validation:validation-api 61/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 javax.validation:validation-api affected?
No. 2.0.1.Final, 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 javax.validation:validation-api should I use?
2.0.1.Final 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 javax.validation:validation-api have?
0 vulnerabilities are recorded for javax.validation:validation-api in the Maven ecosystem: 0 critical, 0 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 javax.validation:validation-api vulnerabilities disclosed?
0 vulnerabilities were recorded for javax.validation:validation-api in the last 12 months. 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 javax.validation:validation-api 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 javax.validation:validation-api for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the javax.validation:validation-api version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.