Active Iq OnecollectApplication · Netapp

CVE-2026-22055

HIGH · 8.8 CVSS v3.1 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
Active IQ OneCollect version 2.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.

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

Active IQ OneCollect version 2.7.3 contains hard-coded credentials embedded in the software that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations. The attacker would need valid low-privilege credentials to authenticate to the system, but could then leverage the hard-coded credentials to access and manipulate AutoSupport functionality beyond their authorized scope.

MitigationUpgrade to a patched version of Active IQ OneCollect that removes the hard-coded credentials. If immediate patching is not possible, restrict network access to the OneCollect service and audit accounts with low-privilege access to minimize the attack surface.

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
Active Iq OnecollectApplication
Affected:= 2.7.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Verify the installed version of Active IQ OneCollect
    Locate the OneCollect installation directory and check for version information in version files, manifest, or executable metadata. On Windows, check Program Files/NetApp/OneCollect or similar paths for a version file. On Linux, check /opt/netapp/onecollect or /usr/local/onecollect.
    Affected if The installed version is exactly 2.7.3
  2. Confirm the OneCollect application is present
    Check if the OneCollect binary or service is installed on the system. Look for onecollect.exe (Windows) or onecollect (Linux) in the installation directory.
    Affected if The application is installed and running version 2.7.3
  3. Inspect application configuration files for hard-coded credentials
    Examine all .conf, .config, .xml, .json, and .properties files in the OneCollect installation directory for embedded username/password pairs, API keys, or secret tokens that appear to be hard-coded rather than referenced from external sources.
    Affected if Hard-coded credentials are found in configuration or application files
  4. Review application binaries for embedded secrets
    Use strings, grep, or a binary analysis tool to search OneCollect executables and libraries for suspicious plain-text strings that resemble credentials (e.g., patterns like 'password=', 'apikey=', 'secret=', base64-encoded strings that decode to credentials).
    Affected if Binary files contain strings that appear to be hard-coded credentials

You are affected if NetApp Active IQ OneCollect version 2.7.3 is installed and contains hard-coded credentials in configuration files or application binaries.

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

Upgrade to a patched version of Active IQ OneCollect that removes the hard-coded credentials. If immediate patching is not possible, restrict network access to the OneCollect service and audit accounts with low-privilege access to minimize the attack surface.

Fix this in Active Iq Onecollect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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