CVE-2026-20094
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 · uneditedA vulnerability in the web-based management interface of Cisco IMC could allow an authenticated, remote attacker with read-only privileges to perform command injection attacks on an affected system and execute arbitrary commands as the root user. This vulnerability is due to improper validation of user-supplied input. An attacker could exploit this vulnerability by sending crafted commands to the web-based management interface of the affected software. A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system as the root user.
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 confidenceCommand injection vulnerability in Cisco IMC web-based management interface allows authenticated users with read-only privileges to execute arbitrary OS commands as root due to improper validation of user-supplied input in crafted HTTP requests.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco IMC presenceDetermine if the target system is a Cisco server with Integrated Management Controller (IMC). Check server model (e.g., Cisco UCS C-Series, M-Series, or B-Series) or inspect BMC firmware type via IPMI or hardware inventory.Affected if The system is a Cisco server running Cisco IMC as its baseboard management controller.
-
Verify IMC web interface is enabledCheck if the Cisco IMC web-based management interface (HTTPS on port 443/4433 or HTTP on port 80/80) is listening and accessible on the management network. Use 'netstat -an | grep -E "(443|80)"' or a port scanner targeting the BMC IP.Affected if The IMC web interface is enabled and reachable, exposing the attack surface.
-
Confirm IMC versionAccess the IMC web login page or use Cisco IMC CLI ('show version' via IPMI or SSH to the BMC) to retrieve the IMC firmware version. Compare the version number against the Cisco IMC version history for CVE-2026-20094.Affected if The installed IMC version falls within the vulnerable version range (if known) or is an unpatched version.
-
Check for existing user accountsList authenticated IMC users via the web interface user management page or via CLI ('show users' or LDAP/Radius integration status) to confirm read-only or privileged accounts exist.Affected if At least one authenticated user account (even read-only) exists in the IMC, allowing HTTP requests to be crafted.
The environment is affected if the system runs Cisco IMC with an accessible web interface and contains at least one authenticated user account, with an unpatched IMC version containing the command injection flaw.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Cisco's vendor patch for CVE-2026-20094 immediately; implement network segmentation to restrict IMC management interface access to trusted management networks as a compensating control until patched.
Upgrade to the fixed Cisco IMC release specified in the Cisco security advisory for CVE-2026-20094 on sec.cloudapps.cisco.com
- Identify the exact version of Cisco IMC (Integrated Management Controller) currently installed on the affected system
- Navigate to Cisco's official security advisory page at sec.cloudapps.cisco.com for CVE-2026-20094
- Locate the specific fixed release version for your Cisco IMC version in the advisory
- Download the fixed Cisco IMC software version from Cisco's official download center
- Plan maintenance window as upgrades may require system downtime
- Follow Cisco's standard IMC software upgrade procedure for your hardware platform (UCS C-Series, UCS S-Series, or UCS Manager)
- After upgrade, verify the new version is installed and the vulnerability is resolved
- Confirm the web-based management interface is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20094 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20094 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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