CVE-2020-11995 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.dubbo:dubbo-parent. A fix is available for org.apache.dubbo:dubbo-parent — see the affected versions and patch details below.
Deserialization exploitation in Apache Dubbo
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.apache.dubbo:dubbo-parent☕org.apache.dubbo:dubbo-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 deserialization vulnerability existed in dubbo 2.7.5 and its earlier versions, which could lead to malicious code execution. Most Dubbo users use Hessian2 as the default serialization/deserialization protool, during Hessian2 deserializing the HashMap object, some functions in the classes stored in HasMap will be executed after a series of program calls, however, those special functions may cause remote command execution. For example, the hashCode() function of the EqualsBean class in rome-1.7.0.jar will cause the remotely load malicious classes and execute malicious code by constructing a malicious request. This issue was fixed in Apache Dubbo 2.6.9 and 2.7.8.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.dubbo:dubbo-parent | ≥ 2.7.0&&< 2.7.8 | 2.7.8org.apache.dubbo:dubbo-parent:2.7.8 |
| ☕Maven | org.apache.dubbo:dubbo-parent | all versions | 2.6.9org.apache.dubbo:dubbo-parent:2.6.9 |
Affected Products
dubboapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.dubbo:dubbo-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.dubbo:dubbo-parent to 2.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11995 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-2020-11995 in your dependencies?
Find it across Maven, including transitive dependencies.