Skip to content
VulniPulse
Medium4.8Cisco Updated

Medium [CVE-2026-20198] Cisco Integrated Management Controller Cross-Site Scripting Vulnerability

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

cisco-sa-cimc-xss-7EhBFxBp Published Aug 5, 2026Updated by vendor Aug 5, 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 web-based management interface of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface.

This vulnerability is due to insufficient validation of user input. An attacker could exploit this vulnerability by persuading a user of an affected interface to click a crafted link.

A successful exploit could allow the attacker to execute arbitrary script code in the browser of the targeted user or access sensitive, browser-based information.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

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

Affected versions
  • Scope: At the time of publication, this vulnerability affected the following Cisco products if they were running a vulnerable release of Cisco IMC, regardless of device configuration:
  • 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 4.3 (first fixed: 4.3(6.260054))
  • Release 6.0 (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

Official advisory · high-confidence parse· fetched 2 hours 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)
  • 4.3(6.260054)
  • 6.0(2.260143)1
  • 3.2.18.1
  • 4.15.4

Official advisory · high-confidence parse· fetched 2 hours 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 this vulnerability.

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