Threats / Cisco / CVE-2025-20281
CVE-2025-20281
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Cisco Identity Services Engine vulnerability
Cisco Identity Services Engine contains an injection vulnerability in its API due to insufficient input validation, allowing remote code execution and root privilege acquisition on affected devices.
Verdict
Today item — known-exploited.
An unauthenticated or low-privileged attacker can submit a crafted API request to exploit insufficient input validation, achieving remote code execution with root-level privileges on ISE and ISE-PIC deployments.
CISA KEV Yes · 2025-07-285EPSS 0.97069 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
47 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-07-28).
Probability (EPSS)
EPSS 0.97069 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Cisco, Identity Services Engine. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-74 CWE-74 — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 33 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious API request containing injection payload targeting the vulnerable ISE endpoint.
Business
Identity and access control infrastructure becomes a direct attack surface for unauthorized code execution.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I submit the request and bypass input validation controls to execute arbitrary code on the target system.
Business
Attacker gains root-level access to critical authentication and policy enforcement systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent control and pivot through the compromised ISE instance to access connected network resources.
Business
Entire identity infrastructure and downstream systems become compromised, enabling lateral movement across the enterprise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05