Skip to content
VulniPulse
Sign in
Advisory severityHigh7.2Cisco Updated

High [CVE-2026-20362] Cisco Finesse Server-Side Request Forgery Vulnerability

This high-severity Cisco advisory covers CVE-2026-20362 affecting Finesse, Unified Contact Center Express.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

cisco-sa-finesse-ssrf-mmSuyugS Source published Source updated

VulniPulse record published Record updated

CVE-2026-20362
Affected products & platforms
CiscoUnified Communications
Open source advisory

Android app · Google Play

Monitor future Cisco CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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.

Affected products named by the advisory: Unified Contact Center Express.

Affected versions
  • Scope: This vulnerability affects Cisco Finesse, regardless of device configuration.
  • 12.6 and earlier — Migrate to a fixed release
  • Release 15.0 (first fixed: 15.0(1) SU3 (Feb 2027))
  • Earlier than 15.0 — Migrate to a fixed release
  • Release 15.0 (first fixed: 15.0(1)ES202701 (Jan 2027))
  • 12.5 and earlier — Migrate to a fixed release
  • Release 15.0 (first fixed: 15.0(1) SU2 (Feb 2027))

Official advisory · high-confidence parse· fetched 11 hours ago·verify at source

Fixed versions
  • 15.0(1) SU3 (Feb 2027)
  • 15.0(1)ES202701 (Jan 2027)
  • 15.0(1) SU2 (Feb 2027)

Official advisory · high-confidence parse· fetched 11 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
  • Release 12.6 and earlier: migrate to a fixed release.
  • Release 15.0: upgrade to 15.0(1) SU3 (Feb 2027).
  • Earlier than 15.0: migrate to a fixed release.
  • Release 15.0: upgrade to 15.0(1)ES202701 (Jan 2027).
  • Release 12.5 and earlier: migrate to a fixed release.
  • Release 15.0: upgrade to 15.0(1) SU2 (Feb 2027).
Workaround status
  • There are no workarounds that address this vulnerability.

Official advisory · high-confidence parse· fetched 11 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.