CVE-2021-36161

CVE-2021-36161 is a critical-severity vulnerability in Apache Dubbo with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-134.

Key facts

Description

Some component in Dubbo will try to print the formated string of the input arguments, which will possibly cause RCE for a maliciously customized bean with special toString method. In the latest version, we fix the toString call in timeout, cache and some other places. Fixed in Apache Dubbo 2.7.13

Frequently asked questions

What is CVE-2021-36161?
Some component in Dubbo will try to print the formated string of the input arguments, which will possibly cause RCE for a maliciously customized bean with special toString method. In the latest version, we fix the toString call in timeout, cache and some other places. Fixed in Apache Dubbo 2.7.13
How severe is CVE-2021-36161?
CVE-2021-36161 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2021-36161 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2021-36161?
CVE-2021-36161 affects Apache Dubbo. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2021-36161?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2021-36161 published?
CVE-2021-36161 was published on 2021-09-09 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Apache Dubbo

All CVEs affecting Apache Dubbo →

Other CWE-134 vulnerabilities

Browse all CWE-134 vulnerabilities →