Vulnerabilities

Cisco UCS Central Vulnerability CVE-2026-76506 Lets Authenticated Attackers Execute Commands

Cisco disclosed CVE-2026-76506 in the UCS Central management interface. A fix is available; exploitation requires valid credentials on the target system.

Cisco UCS Central Vulnerability CVE-2026-76506 Lets Authenticated Attackers Execute Commands

On November 4, Cisco disclosed a high-severity vulnerability in UCS Central Software. CVE-2026-76506 allows remote command execution, file writes or access to sensitive information. An attacker must have valid login credentials for the vulnerable device. Cisco has released fixed software.

What was disclosed

The flaw is in the web-based management interface and is caused by insufficient validation of data sent in HTTP requests. Cisco rated the vulnerability 7.6 on the CVSS scale. The advisory does not report any known malicious exploitation.

The detailed advisory was first published on November 4 at 16:00 GMT, which is 5:00 p.m. Polish time. Cisco had announced the upcoming release in general terms the week before. The new development in this period is the disclosure of the specific vulnerability and the conditions needed to exploit it.

Which deployments to check

According to Cisco, UCS Central is affected regardless of device configuration. For the 2.1 release train, the first fixed release is 2.1(2c). Cisco advises users of version 2.0 and earlier to migrate to a fixed release.

The login requirement narrows the conditions for an attack, but it means the security of administrator accounts, and of any other accounts with access to the management interface, still matters. A risk assessment should consider both the product version and the networks from which the system can be reached. Cisco has not provided a workaround that removes the vulnerability.

What to do now

  • Identify where UCS Central is running and which releases are actually installed.
  • Compare the version against the fixed-release table in the advisory, then schedule an upgrade or migration.
  • Before making changes, check compatibility requirements and back up the configuration.
  • Restrict access to the management interface to authorized administrators and appropriate networks. This adds protection but does not replace the patch.
  • After deployment, confirm the version and verify that management functions work correctly.

SecurHUB’s take

Systems that manage infrastructure need their own access controls and patching process. Security audits help determine whether user permissions and the exposure of management interfaces match their role in the organization.

Sources: Cisco, Tenable, Severity Daily

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk