Skip to main content

Cisco APIC CVE-2026-76488

| EUVDEUVD-2026-94469 MEDIUM
Permissions, Privileges, and Access Controls (CWE-264)
2026-10-07 cisco GHSA-qm4p-mv5x-gc25
6.5
CVSS 3.1 · Vendor: cisco
View

Attack ChainAIDerived

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

  1. Access
    Authenticate with admin credentials to APIC
  2. Delivery
    Submit crafted values in export policy UI fields
  3. Exploit
    Read sensitive filesystem files via weak access control
  4. Execution
    Harvest exposed key materials
  5. Impact
    Elevate to root on APIC and managed switches

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V8 - Authorization Permission and access control
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires valid administrative credentials on the Cisco APIC (PR:H) - this is not a default-configuration remote-unauthenticated bug. The attacker interacts with the export policies functionality and injects crafted values into specific UI fields to abuse insufficient access control to filesystem resources (CWE-264). Key limiting factors: administrative authentication is mandatory, which restricts realistic exploitation to compromised or malicious admin accounts; no user interaction is needed once authenticated (UI:N). The meaningful escalation (to root on APIC and managed switches) depends on sensitive key materials being present and readable on the underlying filesystem.

Impact

This is a moderate-risk, high-privilege information-disclosure flaw rather than a top-priority emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N, base 6.5) shows it is network-reachable with low complexity and no user interaction, but the PR:H requirement is the dominant limiting factor: the vendor description explicitly states the attacker must already hold valid administrative credentials on the APIC. That makes this primarily a post-compromise or malicious/compromised-insider escalation path, not a mass-exploitable perimeter bug. No EPSS score, no CISA KEV listing, and no POC indicator were provided in the input, so there is no signal of active or imminent exploitation - no public exploit identified at time of analysis. The signals are internally consistent (no CVSS-vs-description conflict), though note that the real impact is amplified beyond simple file read: the description says the exposed key materials can be used to elevate to root on the APIC and on managed switches, which justifies the C:H/I:H rating despite the mechanism being file access. Priority should be treated as moderate: significant blast radius if an admin account is compromised, but gated behind administrative authentication.

Exploit ScenarioDerived

An attacker who has obtained valid APIC administrative credentials (e.g., via phishing, credential reuse, or a rogue insider) logs into the controller and, within the export policies functionality, submits crafted values in specific UI fields to read sensitive files from the underlying filesystem. Among the exposed files are key materials that the attacker then uses to escalate to root on the APIC and pivot to managed switches across the ACI fabric. No public exploit code was identified in the provided data.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
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

Sensitive-file disclosure in the export policies feature of Cisco Application Policy Infrastructure Controller (APIC) allows an authenticated remote administrator to submit crafted values in specific UI fields and read files from the device's underlying filesystem, including cryptographic key material. The flaw carries a moderate CVSS score of 6.5 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) and is not remotely exploitable without credentials: valid administrative access is mandatory, and the CVSS vector confirms the high privilege requirement (PR:H) with no user interaction. Because the exposed key material may be usable to escalate to root on the affected APIC and on managed switches in the ACI fabric, the fallout of a successful attack can extend well beyond a single controller; no public exploit code or confirmed active exploitation was identified at time of analysis, and there is no CISA KEV listing.

RemediationAI

No vendor-released patch version is identified in the supplied intelligence, so patch status should be confirmed directly against the Cisco advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apic-info-priv-enAdB5vD before assuming a fix is or is not available; Cisco advisories of this type typically publish fixed software versions, so check that page for the exact APIC release that remediates the flaw and upgrade to it. Until a fix is confirmed and applied, the most effective control is to reduce the population of accounts holding full administrative privileges on APIC (the exploit requires valid admin credentials, PR:H), enforcing least-privilege RBAC roles and removing or disabling unused admin accounts - the trade-off is that shrinking admin roles can break automation or operational workflows that depend on broad permissions, so role changes should be staged and tested. Restrict management-plane access to the APIC GUI and API to a dedicated out-of-band management network or a small set of trusted jump hosts via ACLs or firewall rules; this limits exposure if an admin credential is phished or reused, at the cost of added access friction for legitimate administrators. Review and constrain export policy configurations, removing export policies that are not actively required, and monitor APIC audit logs for unexpected export-policy edits or anomalous UI field values as a detection tripwire; if compromise is suspected, treat the APIC's key material as exposed, rotate certificates and credentials used for controller-to-switch authentication, and consider that fabric switches may need validation given the stated root-escalation path. No public exploit code or active exploitation is known at time of analysis, so these measures are proportionate hardening rather than emergency containment, and the privileged-access prerequisite materially lowers the likelihood of opportunistic attack.

Affected VersionsENISA

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.0(1g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2h)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(7e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(5d)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(6g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(2j)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(7f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2f)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(2f)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2b)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(1j)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(1g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(2h)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(5h)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8h)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(7g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(3f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4d)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2d)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(2g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9c)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9e)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(6h)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8d)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(4h)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8d)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(4c)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8f)
Cisco Application Policy Infrastructure Controller (APIC) 6.1(1f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(5e)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8e)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(6g)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(1d)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(3g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(3d)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(5j)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8f)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9d)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2a)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(3e)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(6c)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8e)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2c)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(2g)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8i)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(8h)
Cisco Application Policy Infrastructure Controller (APIC) 5.3(2e)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(3e)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(9f)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(8g)
Cisco Application Policy Infrastructure Controller (APIC) 6.0(6h)
Cisco Application Policy Infrastructure Controller (APIC) 5.2(5c)

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

Cisco APIC is the software controller for Cisco Application Centric Infrastructure (ACI), providing the policy, fabric-management, and northbound GUI/API layer for Nexus 9000-series switches operating in ACI mode. The vulnerable subsystem is the export policies functionality, which is used to export configuration and related artifacts from the controller. The root cause is classified as CWE-264 (Permissions, Privileges, and Access Controls) - a legacy identifier now folded into CWE-284 (Improper Access Control) - meaning the export-policy code does not sufficiently constrain which filesystem resources a UI-driven operation may reference. Rather than a memory-safety or injection flaw, this is an authorization/validation gap: attacker-supplied values in specific export-policy UI fields are passed through to file-handling routines without adequate path or resource restrictions, allowing reads of files outside the intended export scope. The confidentiality and integrity impact ratings are both High (C:H/I:H) with no availability impact, which is consistent with an attacker reading - and potentially manipulating - sensitive files rather than crashing the service. The CPE entry cpe:2.3:a:cisco:cisco_application_policy_infrastructure_controller_(apic):*:*:*:*:*:*:*:* uses wildcard versioning, indicating the advisory does not enumerate a bounded version range in the supplied data, so version scoping must be confirmed against the Cisco advisory. The stated escalation path - extraction of key materials enabling root on the APIC and on managed switches - reflects the trust model of ACI, where the controller holds credentials and certificates used to authenticate to fabric switches; compromise of those secrets can translate controller-level access into fabric-wide administrative or root-level control.

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 6.5 MEDIUM
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable UI exploited with low complexity and no interaction, but mandatory admin credentials force PR:H; file-read plus root key material exposure yields C:H/I:H, no availability impact.

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

Primary rating from Vendor (cisco).

CVSS VectorVendor: cisco

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

DescriptionCVE.org

A vulnerability in the export policies functionality of Cisco Application Policy Infrastructure Controller (APIC) could allow an authenticated, remote attacker to access sensitive files on an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials.

This vulnerability is due to insufficient access control to file system resources. An attacker could exploit this vulnerability by submitting crafted values in specific UI fields. A successful exploit could allow the attacker to access sensitive files from the underlying file system of an affected device, including key materials that could be used to elevate privileges to root on the affected APIC and on managed switches.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Medium
Cisco ACI data-center controller, common in enterprise fabrics but not universal
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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

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

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

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