dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-8654

HIGH · 8.7 CVSS v4.0 Published 2026-05-15
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
Improper input validation in Delphix Continuous Data connectors allows an authenticated user to execute arbitrary operating system commands on the staging or target host.

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 · moderate confidence

Improper input validation in Delphix Continuous Data connectors allows authenticated users to inject and execute arbitrary operating system commands on connected staging or target hosts. This command injection vulnerability stems from insufficient sanitization of user-supplied input that gets passed to system shell operations.

MitigationApply vendor-supplied patches or updates for Delphix Continuous Data connectors to implement proper input validation and sanitization. Until a patch is available, restrict connector access to only trusted authenticated users and monitor for suspicious command execution activity.

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:X

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 Delphix Continuous Data connector installation
    Search for Delphix connector software on staging and target hosts. Common locations: /opt/delphix, /usr/local/delphix, or check installed packages for 'delphix' or 'connector' names using 'rpm -qa | grep -i delphix' or 'dpkg -l | grep -i delphix' on Linux systems.
    Affected if Delphix Continuous Data connector software is found on the system
  2. Determine connector version
    Run 'dxctl --version' or 'connector --version' if available, check /opt/delphix/version file, or consult the Delphix administration console for connector version information.
    Affected if Version cannot be determined or is not explicitly listed as patched
  3. Verify connector authentication is enabled
    Review connector configuration files (typically in /opt/delphix/etc or under the connector install directory) for authentication settings. Check if user authentication is enforced for connector operations.
    Affected if Connector allows unauthenticated or weakly authenticated access to command execution interfaces
  4. Review connector logs for command injection indicators
    Examine connector logs in /opt/delphix/logs or the logs directory for entries containing suspicious patterns: unexpected shell metacharacters (; | & $ `), multiple commands chained together, or unusual OS command executions.
    Affected if Logs contain evidence of arbitrary command execution or injection attempts
  5. Check for unexpected OS-level processes or scheduled tasks
    On staging and target hosts, review running processes and cron/scheduled tasks for anything spawned by the connector user account that appears unrelated to normal data operations.
    Affected if Unexpected processes or scheduled tasks are present that originate from connector operations
  6. Audit connector user accounts and access patterns
    Review which user accounts have connector access, check for accounts with elevated privileges, and examine recent authentication logs for the connector user for signs of unauthorized access or unusual command execution patterns.
    Affected if Connector access is granted to untrusted users or shows anomalous execution patterns

A user is affected if Delphix Continuous Data connector software is present and authenticated users can supply input that reaches OS-level command execution without sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or updates for Delphix Continuous Data connectors to implement proper input validation and sanitization. Until a patch is available, restrict connector access to only trusted authenticated users and monitor for suspicious command execution activity.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8654 — 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-2026-8654 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