dbcve.org
Intersight Device ConnectorApplication · Cisco

CVE-2026-5944

HIGH · 8.2 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to after 7.5.0 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An improper access control vulnerability exists in the Cisco Intersight Device Connector for Nutanix Prism Central. The service exposes an API passthrough endpoint on TCP port 7373 that is accessible within the network scope of the deployment environment without authentication. An unauthenticated attacker with network access can exploit this vulnerability by sending crafted requests to the exposed endpoint to enumerate cluster metadata, including virtual machine information and cluster configuration details. While the API primarily supports read-only operations, it also allows certain cluster maintenance workflows to be invoked. Although this vulnerability does not allow persistent modification of system configurations or access to credentials or sensitive user data, successful exploitation may result in disruption of active workloads, leading to loss of service availability within the affected environment.

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

An improper access control vulnerability in Cisco Intersight Device Connector for Nutanix Prism Central exposes an unauthenticated API passthrough endpoint on TCP port 7373. Attackers with network access can enumerate cluster metadata including VM information and cluster configuration, and invoke certain cluster maintenance operations, potentially disrupting active workloads.

MitigationImplement proper authentication and authorization controls on the exposed API endpoint (port 7373), and restrict network access to trusted sources to prevent unauthorized access.

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
Intersight Device ConnectorApplication
Affected:>= 4.3.0, <= 7.5.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Cisco Intersight Device Connector installation
    Locate the Intersight Device Connector installation directory or check for the service process on the Nutanix Prism Central host. Look for the connector software package or service daemon.
    Affected if The Cisco Intersight Device Connector software is not installed on the system.
  2. Determine installed version
    Query the installed version of Cisco Intersight Device Connector using the system's package manager, connector management interface, or version file within the installation directory. Compare the version number against the affected range >= 4.3.0 and <= 7.5.0.
    Affected if The installed version falls within 4.3.0 through 7.5.0 inclusive.
  3. Verify TCP port 7373 is listening
    Run a port scan or use netstat/ss commands on the Prism Central host to check if TCP port 7373 is open and listening for connections.
    Affected if Port 7373 is open and accepting connections.
  4. Check network exposure of port 7373
    Review firewall rules, network ACLs, or security group configurations to determine whether port 7373 is accessible from untrusted network segments or the public internet versus being restricted to localhost or authorized management networks.
    Affected if Port 7373 is accessible from untrusted or external network addresses.
  5. Confirm API passthrough functionality is enabled
    Inspect the Intersight Device Connector configuration settings or registry to verify whether the API passthrough endpoint feature is currently enabled in the connector settings.
    Affected if The API passthrough endpoint feature is enabled in the connector configuration.

A user is affected if Cisco Intersight Device Connector version 4.3.0 through 7.5.0 is installed with TCP port 7373 open and accessible from untrusted networks while the API passthrough feature remains enabled.

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
Upgrade available Upgrade to a release after 7.5.0
Interim mitigation

Implement proper authentication and authorization controls on the exposed API endpoint (port 7373), and restrict network access to trusted sources to prevent unauthorized access.

Fix this in Intersight Device Connector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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