InsightiqApplication · Dell

CVE-2026-35071

HIGH · 8.2 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 6.3.0 or later.
See remediation →
84/100
Remediation priority · High
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
Dell PowerScale InsightIQ, versions 6.0.0 through 6.2.0, contains an improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Command execution.

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

Dell PowerScale InsightIQ versions 6.0.0 through 6.2.0 contains an OS Command Injection vulnerability where improper neutralization of special elements in input allows a high-privileged attacker with local access to execute arbitrary commands on the underlying operating system.

MitigationApply the vendor-supplied patch or upgrade to a patched version beyond 6.2.0 once available. Restrict local access to trusted, privileged users only until the patch is applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InsightiqApplication
Affected:>= 6.0.0, < 6.3.0

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

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. Determine installed InsightIQ version
    Locate the Dell InsightIQ installation and retrieve its version number using system inventory tools, package manager queries, or application metadata files (e.g., RPM/dpkg queries, installation logs, or the application GUI About section)
    Affected if The installed version is 6.0.0, 6.0.x, 6.1.x, or 6.2.0 (or any version >= 6.0.0 and < 6.3.0)
  2. Confirm InsightIQ service is running
    Check if the Dell InsightIQ application or web service is active on the system using process listing commands (ps, service status) or system service management tools
    Affected if The vulnerable software version is running and accessible on the system
  3. Verify high-privileged local access exists
    Review local user accounts with elevated privileges on the InsightIQ host, particularly administrative or root-level access that could potentially exploit the command injection flaw
    Affected if Untrusted or unauthorized high-privileged local users exist on the system hosting InsightIQ

The environment is affected if InsightIQ version is 6.0.0 through 6.2.0 (or any version < 6.3.0) and the service is running with potential local attacker access.

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
Upgrade available Upgrade to 6.3.0 or later
Fixed in 6.3.0
Interim mitigation

Apply the vendor-supplied patch or upgrade to a patched version beyond 6.2.0 once available. Restrict local access to trusted, privileged users only until the patch is applied.

Recommended fix High confidence

6.3.0 or later stable release

  1. 1. Back up the current InsightIQ configuration and data according to Dell backup procedures
  2. 2. Review the Dell PowerScale InsightIQ 6.3.0 release notes for any pre-upgrade requirements or known issues
  3. 3. Schedule a maintenance window as the upgrade may require service downtime
  4. 4. Download the InsightIQ 6.3.0 (or latest stable) installer from Dell support portal (www.dell.com/support)
  5. 5. Follow Dell's documented upgrade procedure for InsightIQ, typically running the installer with appropriate privileges
  6. 6. Verify the upgrade was successful by checking the version number in the InsightIQ admin interface
  7. 7. Validate that all expected functionality is working post-upgrade
  8. 8. Confirm the vulnerability is resolved by verifying the version is now >= 6.3.0
Caveat Review Dell release notes for any configuration or feature changes between 6.0.0-6.2.0 and 6.3.0; some features or APIs may have changed behavior

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

Fix this in Insightiq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-35071 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