Skip to content
VulniPulse
Sign in
Advisory severityHigh8.8Cisco PoC reported

High [CVE-2026-20200 +1] Cisco Integrated Management Controller Argument Injection Vulnerabilities

This high-severity Cisco advisory covers CVE-2026-20200 and CVE-2026-20288 affecting Unified Computing System (Standalone), Unified Computing System E-Series Software (UCSE).

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 2 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.

cisco-sa-cimc-arg-inject-upSHdMfU Source published Source updated

VulniPulse record published Record updated

CVE-2026-20200CVE-2026-20288
Affected products & platforms
CiscoUnclassified
Open source 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
Get CVE alertsSee app features

Summary

Multiple vulnerabilities in the web-based management interface of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected system and elevate privileges to root.

For more information about these vulnerabilities, see the Details section of this advisory.

Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.

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

Affected versions
  • Earlier than 4.12 — Migrate to a fixed release
  • Release 4.12 (first fixed: 4.12.8)
  • 4.13 — Migrate to a fixed release
  • 4.14 — Migrate to a fixed release
  • Release 4.15 (first fixed: 4.15.6)
  • 4.16 — Migrate to a fixed release
  • Release 4.18 (first fixed: 4.18.5 (Sep 2026))
  • Release 26.1 (first fixed: 26.1.2)
  • Earlier than 4.2 — Migrate to a fixed release
  • Release 4.2 (first fixed: 4.2(3r))
  • Release 4.3 (first fixed: 4.3(2.260020))
  • Release First Fix Release for CVE-2026-20288 (first fixed: Earlier than 4.3)
  • Migrate to a fixed release — Migrate to a fixed release
  • Release 4.3 (first fixed: 4.3(6.260033))
  • Release 4.3(6.260054) (first fixed: 6.0)
  • Release 6.0(2.260044) (first fixed: 6.0(2.260143)1)
  • Release 3.2 and earlier (first fixed: 3.2.18.1)
  • Release 4.15 and earlier (first fixed: 4.15.4)
  • Earlier than 4.3 — Migrate to a fixed release
  • Release 4.3 (first fixed: 4.3(6.260054))

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Fixed versions
  • 4.12.8
  • 4.15.6
  • 4.18.5 (Sep 2026)
  • 26.1.2
  • 4.2(3r)
  • 4.3(2.260020)
  • Earlier than 4.3
  • 4.3(6.260033)
  • 6.0
  • 6.0(2.260143)1
  • 3.2.18.1
  • 4.15.4
  • 4.3(6.260054)

Official advisory · high-confidence parse· fetched 24 days 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.
  • Earlier than 4.12: migrate to a fixed release.
  • Release 4.12: upgrade to 4.12.8.
  • Release 4.13: migrate to a fixed release.
  • Release 4.14: migrate to a fixed release.
  • Release 4.15: upgrade to 4.15.6.
  • Release 4.12: upgrade to 4.12.8.
  • Release 4.13: migrate to a fixed release.
  • Release 4.14: migrate to a fixed release.
Workaround status
  • There are no workarounds that address these vulnerabilities.

Official advisory · high-confidence parse· fetched 24 days 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.