CVE Intelligence
Medium

CVE-2026-20175 — Cisco Finesse File Inclusion Vulnerability

A vulnerability in Cisco Finesse could allow an unauthenticated, remote attacker to load arbitrary files from remote locations into an active user session on an affected device, possibly leading to browser-based attacks. This vulnerability is due to insufficient validation of user-supplied input for HTTP requests that are sent to an affected device. An attacker who has knowledge of the address of the affected device could exploit this vulnerability by persuading a user to click a crafted link that contains the affected device address. A successful exploit could allow the attacker to conduct browser-based attacks and execute arbitrary script code in the context of the affected interface or access sensitive information on the affected device.

Published Jun 3, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: cisco

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.18%
ahead of 7% of scored CVEs · Oct 14, 2026
Affects
Cisco
Finesse
CVSS base
6.1
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Cisco Finesse).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Cisco Finesse version 12.5(1)ES7version 12.5(1)SUversion 12.5(1)_SUversion 12.5(2)version 12.6(1)ES5version 12.6(1)ES4version 12.6(1)ES3version 12.6(1)ES2
and 83 more version 12.5(1)ES8version 12.0(1)ES8version 12.6(1)ES1version 11.6(1)ES11version 12.6(1)ES6version 12.6(1)version 12.0(1)ES7version 12.5(1)ES6version 12.5(1)ES5version 12.0(1)ES6version 12.5(1)ES4version 12.0(1)ES5version 12.5(1)ES3version 12.0(1)ES4version 12.5(1)ES2version 12.6(2)ES2version 12.6(2)ES7version 15.0(1)SU1version 15.0(1)ES202602version 15.0(1)ES202511version 15.0(1)ES202508version 12.6(2)ES6version 15.0(1)version 12.6(2)ES5version 12.6(2)ES4version 12.5(1)SU ES3version 12.6(2)ES3version 12.5(1)ES1version 12.6(1)ES11version 12.5(1)SU ES2version 12.6(1)ES10version 12.6(2)ES1version 12.6(1)ES9version 12.6(1)ES8version 12.6(2)version 12.6(1)ES7_ETversion 12.6(1)ES7version 12.5(1)SU ES1version 11.0(1)ES7version 11.6(1)ES7version 12.0(1)version 11.0(1)ES4version 11.0(1)ES6version 11.6(1)ESversion 11.6(1)ES2version 10.5(1)ES10version 11.6(1)version 11.5(1)version 10.5(1)ES8version 11.5(1)ES4version 10.5(1)ES7version 10.5(1)ES6version 11.0(1)ES3version 11.6(1)ES4version 11.6(1)FIPSversion 11.0(1)version 10.5(1)ES3version 12.0(1)ES2version 11.0(1)ES2version 11.6(1)ES3version 10.5(1)ES4version 10.5(1)ES5version 11.6(1)ES10version 12.0(1)ES3version 12.5(1)version 10.5(1)ES1version 11.5(1)ES6version 11.6(1)ES9version 11.6(1)ES5version 10.5(1)ES9version 11.5(1)ES2version 11.5(1)ES3version 11.0(1)ES_Rollbackversion 11.0(1)ES5version 12.0(1)ES1version 10.5(1)ES2version 11.6(1)ES6version 10.5(1)version 11.0(1)ES1version 11.5(1)ES5version 11.6(1)ES1version 11.5(1)ES1version 11.6(1)ES8
Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.1 CVSS 3.1 Medium 2.8 2.7 psirt@cisco.com via NIST National Vulnerability Database
6.1 CVSS 3.1 Medium — — cisco via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N (score shown at the top: psirt@cisco.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-73

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · cisco/cisco finesse
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.1
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Undergoing Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jun 3, 2026 · cisco

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

Cisco
every CVE for this vendor
CWE-73
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-20362 Cisco Finesse Server-Side Request Forgery Vulnerability 8d
  • Critical CVE-2021-44228 Apache Log4j2 Remote Code Execution Vulnerability KEV Dec 10, 2021

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-20175 is "Cisco Finesse File Inclusion Vulnerability", rated Medium. It affects Finesse (Cisco); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.1 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.