Skip to main content

Cisco APIC EUVDEUVD-2026-94473

| CVE-2026-76500 CRITICAL
Improper Control of a Resource Through its Lifetime (CWE-664)
2026-10-07 cisco GHSA-jcgq-5qqq-gj2g
9.8
CVSS 3.1 · Vendor: cisco
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach APIC management interface over network
  2. Delivery
    Send crafted request to controller
  3. Exploit
    Trigger improper resource lifecycle flaw
  4. Execution
    Execute action with full impact
  5. Impact
    Compromise ACI fabric control plane

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource lifecycle control
Exploitation Conditions

The attacker requires network reachability to the Cisco APIC controller (its management/API plane); per AV:N/PR:N/UI:N the vendor indicates no authentication and no user interaction are needed against the affected software versions. A key limiting factor is that APIC is a data-center SDN controller typically deployed on isolated or restricted management networks, so exploitation depends on the attacker first reaching that management segment. The description does not name any specific feature, protocol, or non-default configuration as a prerequisite - it only states the issue falls under improper resource-lifecycle control (CWE-664) - so the precise triggering condition cannot be extracted and should be confirmed against Cisco advisory cisco-sa-hardening-apic-UOXWtfh.

Impact

This is a Cisco-reported, internally discovered vulnerability in the Cisco Application Policy Infrastructure Controller (APIC) carrying a vendor CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), which on paper implies remote, unauthenticated, low-complexity exploitation with full confidentiality, integrity, and availability impact. However, the severity signals and the real-world signals diverge sharply: there is no EPSS score provided, the CVE is NOT on the CISA KEV list, and no public proof-of-concept is referenced - the status is 'no public exploit identified at time of analysis.' The advisory language ('proactive security and product quality,' 'comprehensive internal security review,' 'software hardening releases') indicates this was found internally by Cisco rather than through observed attacks, strongly suggesting no active exploitation. A major data-quality caveat: the CWE is CWE-664, a broad Pillar-level weakness ('Improper Control of a Resource Through its Lifetime') that conveys no concrete technical detail, and the description explicitly bundles 'multiple internally discovered vulnerabilities' under one identifier, so the 9.8 vector cannot be mapped to a specific exploitable flaw from the data given. The 'Information Disclosure' tag also conflicts with the C:H/I:H/A:H vector, which claims full-triad impact rather than disclosure alone - verify with the Cisco advisory. Net assessment: treat as a high-priority patch for organizations running APIC because of the critical vendor score and the sensitive, high-value nature of the SDN controller, but recognize the real-world exploitation likelihood is presently unquantified and there is no evidence of in-the-wild activity.

Exploit ScenarioDerived

Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N), a remote attacker with network reachability to the APIC management plane sends crafted traffic to the controller to trigger the resource-lifecycle flaw, gaining the ability to compromise confidentiality, integrity, and availability of the data-center fabric controller. No proof-of-concept is publicly available, and the single generic 'hardening' advisory provides no exploitation specifics, so the exact attack primitive cannot be reconstructed from available data.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Unauthenticated remote attackers who can reach the management/API plane of the Cisco Application Policy Infrastructure Controller (APIC) could potentially achieve full compromise of confidentiality, integrity, and availability, as reflected by the CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The issue was discovered by Cisco's own engineering team during an internal security review of APIC and falls under CWE-664, the improper control of a resource through its lifetime; affected coverage in the supplied CPE is a wildcard for all APIC versions, so no specific vulnerable build range is enumerated. At time of analysis there is no public exploit identified and no CISA KEV confirmation, although APIC's role as a data-center SDN controller on typically isolated management networks is the principal practical barrier to exploitation rather than any input-confirmed technical prerequisite.

RemediationAI

Cisco published this issue as part of an internally driven APIC hardening release, so remediation is to upgrade APIC to the fixed software version specified in Cisco Security Advisory cisco-sa-hardening-apic-UOXWtfh (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-apic-UOXWtfh); the supplied data does not include an exact fixed release number, so the version must be read from the advisory rather than assumed, and no vendor-released patch identifier was otherwise provided. Because the advisory groups multiple hardening fixes under one CVE, treat it as a cumulative update and validate the target version covers every listed defect. Until the upgrade is applied, the most effective compensating control is to restrict reachability to the APIC management/API plane: place APIC controllers on a dedicated, segmented management network with strict ACLs, permit only known administrative subnets and jump hosts, disable any unnecessary northbound API exposure or external-facing management access, and log and alert on unexpected connections to the controller - the trade-off is reduced operational flexibility for orchestration tooling and remote administration, and it does not fix the underlying defect if an attacker already has a foothold on the management segment. Additional hardening such as limiting API access to authenticated service accounts, enforcing rate limiting to blunt resource-exhaustion style abuse of lifecycle handling, and monitoring APIC for process crashes, memory growth, or unexpected restarts (which can indicate use-after-free or resource-leak triggers) can provide earlier detection; these measures reduce exposure and improve visibility but do not remove the vulnerability, so upgrading remains the only complete fix.

Affected VersionsENISA

Cisco Application Policy Infrastructure Controller (APIC) 5.3(2a)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2c)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(3d)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(7g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4d)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(5d)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(3g)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(4h)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(7e)
Cisco Application Policy Infrastructure Controller (APIC) 6.2(1f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(6g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(1g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(6c)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8i)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(5j)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2d)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4e)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(2j)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8d)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2b)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(1j)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(3g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(6h)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2h)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4h)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(5e)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(3g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(6e)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(1f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2f)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(3e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(3f)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2f)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(3e)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9c)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8f)
Cisco Application Policy Infrastructure Controller (APIC) 6.2(1g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(6h)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8h)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(1d)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(2h)
Cisco Application Policy Infrastructure Controller (APIC) 6.2(2e)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(3f)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8h)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(4c)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(2f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(7f)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(6g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(5c)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(1g)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(5e)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(2g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4f)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(5h)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8d)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9d)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-664 is a CWE Pillar - 'Improper Control of a Resource Through its Lifetime' - meaning the root-cause class is resource lifecycle management: creation, initialization, tracking, and eventual release of a resource (memory buffers, file descriptors, sessions, locks, or protocol state objects). Concrete weaknesses grouped under this pillar include missing release of a resource after an effective lifetime, use-after-free, double-free, and uncontrolled resource consumption, so the specific triggering defect is intentionally not disclosed and must be confirmed against Cisco advisory cisco-sa-hardening-apic-UOXWtfh. The affected technology is the Cisco APIC, the controller component of Cisco's Application Centric Infrastructure (ACI) software-defined networking stack, which exposes a northbound management/API surface; the CPE cpe:2.3:a:cisco:cisco_application_policy_infrastructure_controller_(apic):*:*:*:*:*:*:*:* indicates the advisory applies across APIC releases without pinning a version. Because this is a vendor hardening advisory bundling multiple internally discovered issues under a single CVE identifier, the network attack vector (AV:N), low complexity (AC:L), no privileges (PR:N), and no user interaction (UI:N) indicate the flaw is reachable directly over the network against the affected software versions, but the description does not name a specific feature, protocol, or non-default configuration required to trigger it.

Know when Cisco Application Policy Infrastructure Controller Apic gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cisco) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Description lacks technical detail, so this mirrors the vendor's network/unauthenticated vector for a remotely reachable controller; confidence is low given the generic CWE-664 Pillar and bundled issues.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (cisco).

CVSS VectorVendor: cisco

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Application Policy Infrastructure Controller (APIC) engineering team has conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.  

The vulnerabilities tracked by CVE-2026-76500 are related to issues with improper control of a resource through its lifetime that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-664.

Executive ViewAI

Why It Matters

Cisco APIC, the data-center SDN controller, is affected by a critical unauthenticated remote vulnerability that could allow full compromise of confidentiality, integrity, and availability when its management/API plane is reachable. No vendor-released patch is identified at time of analysis, so leadership should prioritize reducing exposure of APIC management interfaces and preparing for emergency patching. A successful attack could disrupt data-center network policy and operations, making this a severe business risk despite no public exploit identified at time of analysis.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis; restrict APIC management/API plane access to trusted administrative networks, enforce strict segmentation/firewalling, and monitor for unauthorized access attempts.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Medium
Cisco SDN controller deployed only in ACI data-center fabrics, not everywhere
Social Media
2
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy