cisco-sa-finesse-ssrf-mmSuyugSHighCVSS 7.2

Cisco Finesse Server-Side Request Forgery Vulnerability

Published
October 7, 2026
Last Modified
October 29, 2026

🔗 CVE IDs covered (1)

CVE-2026-20362 →

📋 Description

A vulnerability in the web-based management interface of Cisco Finesse could allow an unauthenticated, remote attacker to conduct server-side request forgery (SSRF) attacks through an affected device.

This vulnerability is due to improper input validation for specific HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to obtain limited sensitive information for services that are associated with the affected device.

Cisco plans to release software updates that address this vulnerability. There are no workarounds that address this vulnerability.

CVE-2026-20362 — Cisco Finesse Server-Side Request Forgery Vulnerability (CVSS 3.1 7.2, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N)

🎯 Affected products30

  • Cisco Finesse
  • Cisco Unified Contact Center Express
  • Cisco Finesse 12.6(1)
  • Cisco Finesse 12.6(1)ES1
  • Cisco Finesse 12.6(1)ES10
  • Cisco Finesse 12.6(1)ES11
  • Cisco Finesse 12.6(1)ES2
  • Cisco Finesse 12.6(1)ES3
  • Cisco Finesse 12.6(1)ES4
  • Cisco Finesse 12.6(1)ES5
  • Cisco Finesse 12.6(1)ES6
  • Cisco Finesse 12.6(1)ES7
  • Cisco Finesse 12.6(1)ES7_ET
  • Cisco Finesse 12.6(1)ES8
  • Cisco Finesse 12.6(1)ES9
  • Cisco Finesse 12.6(2)
  • Cisco Finesse 12.6(2)ES1
  • Cisco Finesse 12.6(2)ES2
  • Cisco Finesse 12.6(2)ES3
  • Cisco Finesse 12.6(2)ES4
  • Cisco Finesse 12.6(2)ES5
  • Cisco Finesse 12.6(2)ES6
  • Cisco Finesse 12.6(2)ES7
  • Cisco Finesse 12.6(2)ES8
  • Cisco Finesse 15.0(1)
  • Cisco Finesse 15.0(1)ES202508
  • Cisco Finesse 15.0(1)ES202511
  • Cisco Finesse 15.0(1)ES202602
  • Cisco Finesse 15.0(1)SU1
  • Cisco Finesse 15.0(1)SU2

✅ Remediation

Cisco has released software updates that address this vulnerability. https://software.cisco.com Workarounds: There are no workarounds that address this vulnerability.

🔗 References (2)