dbcve.org
Aiops CollectorApplication · Dell

CVE-2026-32652

HIGH · 7.8 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 1.18.3 or later.
See remediation →
80/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 AIOps Collector versions prior to 1.18.3 contain a "Use of Default Credentials" vulnerability. A low privileged attacker with console access could potentially exploit this vulnerability to gain Filesystem access. This vulnerability only affects fresh installations of Collector versions earlier than 1.18.3. Systems that have been upgraded (either manually or automatically) to version 1.18.3 or later are not impacted, even if they were originally installed on an earlier version.

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 AIOps Collector versions prior to 1.18.3 ship with default credentials that can be exploited by a low-privileged attacker with console access to gain filesystem access. This vulnerability only impacts fresh installations, not systems that were upgraded to 1.18.3 or later.

MitigationUpgrade Dell AIOps Collector to version 1.18.3 or later. For existing fresh installations, change default credentials immediately or perform an upgrade to remediate.

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
Aiops CollectorApplication
Affected:< 1.18.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Identify installed Dell AIOps Collector version
    Run 'helm list -A' or check the deployment manifest for the Dell AIOps Collector version, or query the running container/image for its version metadata
    Affected if version is below 1.18.3
  2. Determine installation type
    Check whether this was a fresh installation or an upgrade from a prior version. Review deployment history, backup logs, or check if a previous version tag exists in the container registry
    Affected if this is a fresh installation rather than an upgrade from an earlier version
  3. Verify default credentials status
    Examine the configuration files, secrets, or deployment manifests for embedded/default usernames and passwords. Check if the default admin credentials (typically found in installation documentation or default config files) are still active in the system
    Affected if default credentials are still configured and active in the deployment
  4. Confirm console access exposure
    Review network policies, service exposure, and authentication settings to determine if the management console is accessible and whether it accepts the default credentials
    Affected if console is accessible and default credentials provide valid authentication

A system is affected if it is a fresh installation (not an upgrade) of Dell AIOps Collector version prior to 1.18.3 with default credentials still active and the console accessible to a low-privileged attacker.

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 1.18.3 or later
Fixed in 1.18.3
Interim mitigation

Upgrade Dell AIOps Collector to version 1.18.3 or later. For existing fresh installations, change default credentials immediately or perform an upgrade to remediate.

Recommended fix High confidence

1.18.3 or later

  1. Verify current Aiops Collector version by accessing the Collector console or using the version check command
  2. Download Aiops Collector version 1.18.3 or later from Dell support (support.dell.com) using valid credentials
  3. Follow Dell's documented upgrade procedure for Aiops Collector - typically involves backing up configuration data, stopping the Collector service, installing the new version, and verifying the upgrade
  4. After upgrade, confirm the version is 1.18.3 or later by checking the Collector console or version command
  5. Ensure any default credentials have been changed according to Dell's post-installation security guidance
  6. For systems that cannot be upgraded immediately, restrict console access to trusted personnel only and monitor for unauthorized access attempts

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

Fix this in Aiops Collector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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