CVE-2020-10740 — wildfly-parent
HIGHCVE-2020-10740 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in org.wildfly:wildfly-parent. A fix is available for org.wildfly:wildfly-parent — see the affected versions and patch details below.
Wildfly Unsafe Deserialization Vulnerability
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
org.wildfly:wildfly-parentReal-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
A vulnerability was found in Wildfly in versions before 20.0.0.Final, where a remote deserialization attack is possible in the Enterprise Application Beans(EJB) due to lack of validation/filtering capabilities in wildfly.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wildfly:wildfly-parent | all versions | 20.0.0.Finalorg.wildfly:wildfly-parent:20.0.0.Final |
Affected Products
wildflyredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly:wildfly-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly:wildfly-parent to 20.0.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10740 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
There is currently no known mitigation for this issue.Source: Red Hat security advisory for CVE-2020-10740 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| EAP-CD 20 Tech Preview | wildfly | RHSA-2020:3585 |
| Red Hat Fuse 7.8.0 | wildfly | RHSA-2020:5568 |
| Red Hat JBoss EAP 7.2 | see advisory | RHSA-2020:3144 |
| Red Hat JBoss Enterprise Application Platform 7 | see advisory | RHSA-2020:3642 |
| Red Hat JBoss Enterprise Application Platform 7 | wildfly | RHSA-2020:3143 |
| Red Hat JBoss Enterprise Application Platform 7 | wildfly | RHSA-2020:3464 |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | eap7-glassfish-el-0:3.0.1-4.b08_redhat_00005.1.ep7.el7 | RHSA-2025:9582 |
| Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6 | eap7-jboss-ejb-client-0:4.0.33-2.SP1_redhat_00001.1.el6eap | RHSA-2020:3142 |
Frequently Asked Questions
Is CVE-2020-10740 in your dependencies?
Find it across Maven, including transitive dependencies.