Vulnerability Database · Maven · Package report
dom4j:dom4j: vulnerability history, versions and safety
dom4j:dom4j 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 dom4j:dom4j 20040902.021138 i
Updated on 23 Oct 2026
Good news: 20040902.021138, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Not enough data
What to do: Stay on 20040902.021138 or newer. This can change: a vulnerability disclosed tomorrow can affect 20040902.021138 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 20040902.021138 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 270 packages i
- Last release 253 months ago 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 dom4j:dom4j, 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.
- 20040902.021138 19 Sep 2005
- 1.4 02 Aug 2005
- 1.5 02 Aug 2005
- 1.5-beta-2 02 Aug 2005
- 1.5-rc1 02 Aug 2005
- 1.5.1 02 Aug 2005
- 1.5.2 02 Aug 2005
- 1.6 02 Aug 2005
- 1.6.1 02 Aug 2005
- 1.4-dev-3 02 Aug 2005
- 1.4-dev-4 02 Aug 2005
- 1.4-dev-5 02 Aug 2005
- 1.4-dev-6 02 Aug 2005
- 1.4-dev-7 02 Aug 2005
- 1.4-dev-8 02 Aug 2005
- 1.1 02 Aug 2005
- 1.3 02 Aug 2005
- 1.4-dev-2 02 Aug 2005
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 20040902.021138 | 19 Sep 2005 | none | — | — | Details → |
| 1.4 | 02 Aug 2005 | none | — | — | Details → |
| 1.5 | 02 Aug 2005 | none | — | — | Details → |
| 1.5-beta-2 | 02 Aug 2005 | none | — | — | Details → |
| 1.5-rc1 | 02 Aug 2005 | none | — | — | Details → |
| 1.5.1 | 02 Aug 2005 | none | — | — | Details → |
| 1.5.2 | 02 Aug 2005 | none | — | — | Details → |
| 1.6 | 02 Aug 2005 | none | — | — | Details → |
| 1.6.1 | 02 Aug 2005 | none | — | — | Details → |
| 1.4-dev-3 | 02 Aug 2005 | none | — | — | Details → |
| 1.4-dev-4 | 02 Aug 2005 | none | — | — | Details → |
| 1.4-dev-5 | 02 Aug 2005 | none | — | — | Details → |
| 1.4-dev-6 | 02 Aug 2005 | none | — | — | Details → |
| 1.4-dev-7 | 02 Aug 2005 | none | — | — | Details → |
| 1.4-dev-8 | 02 Aug 2005 | none | — | — | Details → |
| 1.1 | 02 Aug 2005 | none | — | — | Details → |
| 1.3 | 02 Aug 2005 | none | — | — | Details → |
| 1.4-dev-2 | 02 Aug 2005 | none | — | — | Details → |
All 18 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for dom4j:dom4j
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 dom4j:dom4j
Is dom4j:dom4j safe to use?
Vulert has no vulnerabilities on record for dom4j:dom4j 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 dom4j:dom4j's Vulert package health score?
Vulert scores dom4j:dom4j 69/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 dom4j:dom4j affected?
No. 20040902.021138, 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 dom4j:dom4j should I use?
20040902.021138 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 dom4j:dom4j have?
0 vulnerabilities are recorded for dom4j:dom4j 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 dom4j:dom4j vulnerabilities disclosed?
0 vulnerabilities were recorded for dom4j:dom4j 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 dom4j:dom4j 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 dom4j:dom4j for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dom4j:dom4j version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.