Medium [CVE-2026-20321] Cisco Application Policy Infrastructure Controller API Command Injection Vulnerability
This medium-severity Cisco advisory covers CVE-2026-20321 affecting Application Policy Infrastructure Controller (APIC).
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
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 34 official vendor sources and 160+ reviewed platform categories.
Summary
A vulnerability in the web-based management API for Cisco Application Policy Infrastructure Controller (APIC) could allow an authenticated, remote attacker to execute arbitrary commands as the root user. To exploit this vulnerability, the attacker must have valid administrative credentials.
This vulnerability is due to insufficient input validation of user-controlled command arguments. An attacker could exploit this vulnerability by authenticating using the API and sending crafted input.
A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system of an affected device with root-level privileges.
Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
This advisory is part of a group of advisories. For a complete list of the advisories and links to them, see Cisco Advance Notification for Publication of October 7, 2026, Security Advisories.
For further documentation of improvements and fixes in Cisco APIC, see Cisco Application Policy Infrastructure Controller Security Hardening Release: October 2026.
- Scope: At the time of publication, this vulnerability affected Cisco APIC, regardless of device configuration.
- 5.3 and earlier — Migrate to a fixed release
- Release 6.0 (first fixed: 6.0(9h))
- Release 6.1 (first fixed: 6.1(6g))
- Release 6.2 (first fixed: 6.2(3g))
Official advisory · high-confidence parse· fetched 11 hours ago·verify at source
- 6.0(9h)
- 6.1(6g)
- 6.2(3g)
Official advisory · high-confidence parse· fetched 11 hours ago·verify at source
Mitigation checklist
- Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
- Release 5.3 and earlier: migrate to a fixed release.
- Release 6.0: upgrade to 6.0(9h).
- Release 6.1: upgrade to 6.1(6g).
- Release 6.2: upgrade to 6.2(3g).
- There are no workarounds that address this vulnerability.
Official advisory · high-confidence parse· fetched 11 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.