CVE-2019-16891 — release.portal.bom
CRITICALCVE-2019-16891 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in com.liferay.portal:release.portal.bom. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for com.liferay.portal:release.portal.bom — see the affected versions and patch details below.
Liferay Portal Allows RCE via Deserialization of a JSON Payload
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.liferay.portal:release.portal.bomReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Liferay Portal CE 7.1.0 and earlier allows remote command execution because of deserialization of a JSON payload.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.portal:release.portal.bom | all versions | 7.1.1com.liferay.portal:release.portal.bom:7.1.1 |
Affected Products
liferay portalliferayResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.portal:release.portal.bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.portal:release.portal.bom to 7.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16891 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2019-16891 in your dependencies?
Find it across Maven, including transitive dependencies.