Loading vulnerability…
A remote code execution vulnerability exists in Apache Dubbo versions 2.7.6 and below due to insecure deserialization of RPC request parameters. An attacker can craft RPC requests with arbitrary service or method names and supply malicious serialized payloads. When Dubbo deserializes these parameters, attacker-controlled code can be executed on the server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is the official Apache Dubbo Spring Boot integration project, containing core modules, auto-configuration, actuator support, and multiple sample applications. Of particular interest is the sample in 'dubbo-spring-boot-samples/auto-configure-samples/consumer-sample', which demonstrates a Java deserialization exploit against a Dubbo provider. The consumer constructs a malicious payload using Rome and marshalsec gadgets, embedding a JNDI LDAP reference (ldap://127.0.0.1:8087/Exploit), and sends it to the provider's DemoService.commonTest(Object o) method via Dubbo RPC (targeting 127.0.0.1:12345). If the provider is vulnerable (i.e., it deserializes untrusted data), this can result in remote code execution via JNDI. The exploit is operational and demonstrates a real attack vector, but is not weaponized for mass exploitation. The rest of the repository consists of Dubbo Spring Boot integration code, configuration, and test cases.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.