Cloud Data Fusion CVE-2025-9571
HIGHSeverity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Red
Network-reachable artifact upload with low complexity and no user interaction, gated by a low-privilege authenticated account (PR:L); deserialization yields full code execution so C/I/A all High, scope unchanged within the instance.
Primary rating from Vendor (f45cbf4e-4146-4068-b7e1-655ffc2c548c).
CVSS VectorVendor: f45cbf4e-4146-4068-b7e1-655ffc2c548c
Lifecycle Timeline
2DescriptionCVE.org
A remote code execution (RCE) vulnerability exists in Google Cloud Data Fusion. A user with permissions to upload artifacts to a Data Fusion instance can execute arbitrary code within the core AppFabric component. This could allow the attacker to gain control over the Data Fusion instance, potentially leading to unauthorized access to sensitive data, modification of data pipelines, and exploration of the underlying infrastructure.
The following CDAP versions include the necessary update to protect against this vulnerability: * 6.10.6+
- 6.11.1+
Users must immediately upgrade to them, or greater ones, available at: https://github.com/cdapio/cdap-build/releases .
AnalysisAI
Remote code execution in Google Cloud Data Fusion (built on the CDAP platform) allows an authenticated principal who holds artifact-upload permissions on an instance to execute arbitrary code inside the core AppFabric component through unsafe deserialization of a crafted artifact. Successful exploitation gives the attacker control of the Data Fusion instance, enabling unauthorized access to sensitive data, tampering with data pipelines, and reconnaissance of the underlying infrastructure. No public exploit code has been identified at time of analysis, the EPSS score is low (0.44%, 36th percentile), and the issue is not listed in CISA KEV, so it is a credible but non-emergency authenticated RCE that still warrants prompt patching. Vendor-released fixes are available in CDAP 6.10.6+ and 6.11.1+.
Technical ContextAI
The vulnerability is a CWE-502 unsafe deserialization flaw in the AppFabric core component of CDAP, the open-source data integration platform that underpins Google Cloud Data Fusion. CDAP accepts user-supplied artifacts (JARs/plugins) for pipeline execution and deserializes them during processing; because the deserialization path does not sufficiently restrict the classes that can be instantiated, a malicious artifact can trigger code execution within the AppFabric service. Underlying technologies include Java object serialization and the CDAP plugin/artifact framework, which hosts the affected component in Google Cloud Data Fusion instances. The root cause class (unsafe deserialization) means the trigger is a crafted artifact rather than a memory-safety bug, and exploitation hinges on the ability to get that artifact loaded by the platform rather than on network reachability alone.
Affected ProductsAI
CDAP installations prior to 6.10.6 and all 6.11.x releases prior to 6.11.1 are vulnerable, per the vendor's own version guidance, and Google Cloud Data Fusion instances built on these CDAP versions inherit the exposure through the AppFabric component. The flaw maps to the CDAP artifact-upload and deserialization subsystem rather than a standalone CPE-controlled product, so affected deployments are best identified by their CDAP base version (anything below 6.10.6, or 6.11.0). Google's own advisory is published in the Google Cloud security bulletin at https://docs.cloud.google.com/support/bulletins#gcp-2025-076, and fixed CDAP builds are distributed through https://github.com/cdapio/cdap-build/releases.
RemediationAI
Upgrade affected CDAP and Google Cloud Data Fusion deployments to CDAP 6.10.6 or later in the 6.10 line, or 6.11.1 or later in the 6.11 line, using the builds published at https://github.com/cdapio/cdap-build/releases; organizations running Data Fusion through Google Cloud should track and apply the mitigation described in the bulletin at https://docs.cloud.google.com/support/bulletins#gcp-2025-076. Where immediate upgrade is not possible, the most effective compensating control is to treat artifact-upload rights as a privileged capability: restrict it with least-privilege IAM bindings so that only vetted service accounts and CI/CD identities can push artifacts, rotate and scope any tokens that currently hold that permission, and audit/subscribe to Data Fusion and CDAP audit logs for unexpected artifact uploads or executions (the trade-off is reduced developer self-service and possible pipeline-release friction). Additional hardening includes isolating Data Fusion instances in dedicated projects with tightly scoped service accounts and minimal access to downstream data stores, accepting the operational overhead of segregated environments; note that neither of these workarounds removes the underlying deserialization flaw, so they should be considered temporary until the patch is applied.
Same weakness CWE-502 – Deserialization of Untrusted Data
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today