dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-9571

HIGH · 8.7 CVSS v4.0 Published 2025-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 .

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A remote code execution vulnerability in Google Cloud Data Fusion allows a user with artifact upload permissions to execute arbitrary code within the core AppFabric component, granting full control over the instance and access to underlying infrastructure.

MitigationUpgrade CDAP to version 6.10.6+ or 6.11.1+ (or later) as specified in the official GitHub releases.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the CDAP version
    Check the Data Fusion instance version through the Google Cloud Console or via the CDAP API/CLI tools
    Affected if The installed version is earlier than 6.10.6 or 6.11.1, or cannot be determined to be at or above these versions
  2. Verify user has artifact upload permissions
    Review IAM roles and permissions assigned to users in the Data Fusion instance. Specifically check for roles that include artifact upload or pipeline deployment capabilities
    Affected if Users with artifact upload permissions exist in the environment
  3. Confirm AppFabric component is accessible
    Check if the AppFabric REST API endpoints are reachable from the network where potential attackers would operate
    Affected if AppFabric component is exposed and accessible without additional authentication beyond basic IAM
  4. Check for custom artifact deployment activity
    Review Data Fusion audit logs or deployment history for any custom artifact or plugin uploads
    Affected if Custom artifacts have been uploaded to the instance, indicating the vulnerable feature is in use
  5. Assess instance network exposure
    Determine whether the Data Fusion UI and API are accessible from the public internet or only from trusted internal networks
    Affected if The instance is internet-facing and allows authenticated access to users who may have artifact upload permissions

The environment is affected if the CDAP version is earlier than 6.10.6 or 6.11.1 AND users with artifact upload permissions exist with access to the Data Fusion instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CDAP to version 6.10.6+ or 6.11.1+ (or later) as specified in the official GitHub releases.

Recommended fix High confidence

CDAP 6.10.6+ or 6.11.1+ (any later version)

  1. Identify the current CDAP version running your Google Cloud Data Fusion instance
  2. Navigate to https://github.com/cdapio/cdap-build/releases to download the fixed version
  3. Select CDAP version 6.10.6 or higher, OR version 6.11.1 or higher (both contain the security fix)
  4. Review the release notes for any migration or pre-upgrade requirements
  5. Plan a maintenance window following Google Cloud Data Fusion upgrade procedures
  6. Execute the upgrade following the official Google Cloud Data Fusion upgrade documentation
  7. Verify the upgrade was successful and confirm the vulnerability is patched

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA4.0 h
34.0 hours of engineering $5,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9571 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9571 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data