Vulnerability Database · Maven · org.assertj:assertj-core · Version
org.assertj:assertj-core 3.16.0
3.16.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 4.0.0-M1.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 05 May 2020
Licence Apache-2.0
Also known from other sources 1
Newer releases 82
Database updated 23/Oct/2026
Release and licence data published by Maven Central. 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 Vulnerabilities affecting this version
org.assertj:assertj-core 3.16.0 vulnerabilities
1 vulnerability cover org.assertj:assertj-core 3.16.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| XML External Entity (XXE) Vulnerability in AssertJ Core Package | 8.2 high | 3.27.7 | 26 Jan 2026 |
Looking for another version, or everything Vulert holds for org.assertj:assertj-core?
Questions
About org.assertj:assertj-core 3.16.0
Is org.assertj:assertj-core 3.16.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover org.assertj:assertj-core 3.16.0: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 4.0.0-M1, and each entry above names the fixed version to move to.
Which version of org.assertj:assertj-core should I use instead of 3.16.0?
4.0.0-M1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 3.16.0 the latest release of org.assertj:assertj-core?
No. 3.16.0 was published 05 May 2020, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor org.assertj:assertj-core for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.assertj:assertj-core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.