dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-44926

HIGH · 8.8 CVSS v3.1 Published 2026-05-20
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
InfoScale CmdServer before 7.4.2 mishandles access control.

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

InfoScale CmdServer versions prior to 7.4.2 contain an access control vulnerability. The specific nature of the flaw (authentication bypass, authorization weakness, or privilege escalation) is not detailed in available sources. The high CVSS score (8.8) indicates significant exploitability and potential for unauthorized command execution or administrative access.

MitigationUpgrade InfoScale CmdServer to version 7.4.2 or later to resolve the access control vulnerability. Until patched, restrict network access to CmdServer interfaces to trusted management networks only.

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
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. Identify if InfoScale CmdServer is installed
    Look for the CmdServer process or service on the system. On Windows, check Services for 'Veritas InfoScale CmdServer' or similar. On Linux, run 'ps -ef | grep cmdserver' or check /opt/VRTSvcs/bin/ for cmdserver binaries.
    Affected if InfoScale CmdServer process or service is found running on the system
  2. Determine the installed version of InfoScale CmdServer
    Run 'cmdserver -version' or 'cmdserver -v' from the InfoScale installation directory. Alternatively, check the product version via package manager on Linux (rpm -qi VRTSvcs) or Windows installer information.
    Affected if The reported version is lower than 7.4.2 or cannot be determined to be 7.4.2 or higher
  3. Verify the CmdServer service is active and listening
    Check if the CmdServer process is listening on its configured port (typically port 14149 or 14150). Use 'netstat -an | grep 1414' or 'ss -tlnp | grep cmdserver' to identify listening ports.
    Affected if CmdServer is running and accepting network connections on any port
  4. Inspect CmdServer authentication and authorization configuration
    Review configuration files in the InfoScale configuration directory (typically /etc/VRTSvcs/ or the cluster config directory) for cmdserver-related settings, particularly authenication methods and user permission mappings.
    Affected if Authentication is not properly enforced or authorization settings allow non-admin users access to privileged operations

The environment is affected if InfoScale CmdServer is installed with a version lower than 7.4.2 and the CmdServer component is running or configured to run.

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 InfoScale CmdServer to version 7.4.2 or later to resolve the access control vulnerability. Until patched, restrict network access to CmdServer interfaces to trusted management networks only.

Recommended fix High confidence

InfoScale CmdServer 7.4.2 or later

  1. Identify the current version of InfoScale CmdServer installed in your environment
  2. Review the InfoScale CmdServer release notes and documentation for version 7.4.2 to understand changes and requirements
  3. Plan and schedule an upgrade window following Veritas standard upgrade procedures
  4. Backup current InfoScale configuration and data
  5. Upgrade InfoScale CmdServer to version 7.4.2 or later
  6. Verify the upgrade was successful and CmdServer is functioning properly
  7. Validate that access controls are properly enforced post-upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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