Skip to content
VulniPulse
Critical9.8Cisco

Critical [CVE-2026-20093] Cisco Integrated Management Controller Authentication Bypass Vulnerability

This critical-severity Cisco advisory covers CVE-2026-20093 affecting Unified Computing System (Standalone), Unified Computing System E-Series Software (UCSE), Enterprise NFV Infrastructure Software.

cisco-sa-cimc-auth-bypass-AgG2BxTn Published Apr 1, 2026Updated by vendor Apr 1, 2026
Affected products & platforms
CiscoUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Cisco CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A vulnerability in the change password functionality of Cisco Integrated Management Controller (IMC) could allow an unauthenticated, remote attacker to bypass authentication and gain access to the system as Admin. This vulnerability is due to incorrect handling of password change requests.

Affected products named by the advisory: Unified Computing System (Standalone); Unified Computing System E-Series Software (UCSE); Enterprise NFV Infrastructure Software.

Affected versions
  • Scope: This vulnerability affects the following Cisco products if they are running a vulnerable release of Cisco IMC, regardless of device configuration:
  • Release 4.15 and earlier (first fixed: 4.15.5)
  • 4.16 and earlier — Migrate to a fixed release
  • Release 4.18 (first fixed: 4.18.3 (Apr 2026))
  • 4.2 and earlier — Migrate to a fixed release
  • Release 4.3 (first fixed: 4.3(2.260007))
  • 4.2 and earlier — Migrate to a fixed release
  • Release 4.3 (first fixed: 4.3(6.260017))
  • Release 6.0 (first fixed: 6.0(1.250174))
  • Release 3.2 and earlier (first fixed: 3.2.17)
  • Release 4.15 and earlier (first fixed: 4.15.3)

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 4.15.5
  • 4.18.3 (Apr 2026)
  • 4.3(2.260007)
  • 4.3(6.260017)
  • 6.0(1.250174)
  • 3.2.17
  • 4.15.3

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
  • Release 4.15 and earlier: upgrade to 4.15.5.
  • Release 4.16 and earlier: migrate to a fixed release.
  • Release 4.18: upgrade to 4.18.3 (Apr 2026).
  • Release 4.2 and earlier: migrate to a fixed release.
  • Release 4.3: upgrade to 4.3(2.260007).
  • Release 4.2 and earlier: migrate to a fixed release.
  • Release 4.3: upgrade to 4.3(6.260017).
  • Release 6.0: upgrade to 6.0(1.250174).
Workaround status
  • There are no workarounds that address this vulnerability.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.