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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2020-10740 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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 |
Detection & 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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-10740 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2020-10740. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| 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?
O3 Security finds CVE-2020-10740 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.