CVE-2025-20118

MEDIUM
Published Feb 26, 2025 Modified Jul 31, 2025 CWE-212

Description

A vulnerability in the implementation of the internal system processes of Cisco APIC could allow an authenticated, local attacker to access sensitive information on an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials. This vulnerability is due to insufficient masking of sensitive information that is displayed through system CLI commands. An attacker could exploit this vulnerability by using reconnaissance techniques at the device CLI. A successful exploit could allow the attacker to access sensitive information on an affected device that could be used for additional attacks.

Is your site exposed to CVE-2025-20118?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

4.4
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Weakness Type (CWE)

CWE-212 CWE-212

Affected Products

Vendor Product
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller
cisco application_policy_infrastructure_controller

References

Frequently Asked Questions

What is CVE-2025-20118? +
A vulnerability in the implementation of the internal system processes of Cisco APIC could allow an authenticated, local attacker to access sensitive information on an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials. This vulnerability is due to insufficient masking of sensitive information that is displayed through system CLI commands. An attacker could exploit this vulnerability by using reconnaissance techniques at the device CLI. A successful exploit could allow the attacker to access sensitive information on an affected device that could be used for additional attacks. It has a CVSS v3.1 base score of 4.4 (MEDIUM).
How severe is CVE-2025-20118? +
CVE-2025-20118 has a CVSS v3.1 score of 4.4 out of 10, rated MEDIUM. This is a medium-severity vulnerability that should be remediated as part of regular maintenance.
What products are affected by CVE-2025-20118? +
CVE-2025-20118 affects products from cisco, specifically: application_policy_infrastructure_controller. Check the affected products table above for specific version ranges.
How do I check if I'm vulnerable to CVE-2025-20118? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2025-24884

kube-audit-rest is a simple logger of mutation/creation requests to the k8s api. If the "full-elastic-stack" example vector configuration was used …
CVE-2026-53604

nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.3.8, the web handler renderMobileBundle passes …
CVE-2025-65965

Grype is a vulnerability scanner for container images and filesystems. A credential disclosure vulnerability was found in Grype, affecting versions …
CVE-2026-96879

Improper removal of sensitive information before storage or transfer vulnerability in Wikimedia Foundation's Mediawiki - FlaggedRevs extension through 1.46.0.
CVE-2026-42880 9.6

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From versions 3.2.0 to before 3.2.11 and 3.3.0 to …
CVE-2026-85094 8.8

The Canva Android App before 2.376.0 did not restrict the headers returned to an external origin running in a privileged …

Don't wait for an exploit

Scan your website for vulnerabilities like CVE-2025-20118 — free, no signup required.