CVE intelligence and bounded remediation

CVE-2025-20276 — Cisco Unified Contact Center Express security vulnerability

High CVSS 7.2

A vulnerability in the web-based management interface of Cisco Unified CCX could allow an authenticated, remote attacker to execute arbitrary code on an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials.  This vulnerability is due to insecure deserialization of Java objects by the affected software. An attacker could exploit this vulnerability by sending a crafted Java object to an affected device. A successful exploit could allow the attacker to execute arbitrary code on the underlying operating system of an affected device as a low-privilege user. A successful exploit could also allow the attacker to undertake further actions to elevate their privileges to root.

Severity
High
CVSS
7.2 (3.1)
Published
2025-06-04
CISA KEV
Not currently listed
Ecosystem
java/maven
Weaknesses
CWE-502

Affected products

  • cisco / unified_contact_center_express / 8.5(1)
  • cisco / unified_contact_center_express / 9.0(2)su3es04
  • cisco / unified_contact_center_express / 10.0(1)su1
  • cisco / unified_contact_center_express / 10.0(1)su1es04
  • cisco / unified_contact_center_express / 10.5(1)
  • cisco / unified_contact_center_express / 10.5(1)su1

Showing 6 representative product identities from 60 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Unsafe deserialization and object reconstruction

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory serialization formats accepted from requests, queues, caches, files, cookies, and cross-service messages.
  • Trace whether untrusted input can select classes, types, callbacks, constructors, or object hooks during decoding.
  • Identify signing, schema validation, trust-boundary, and compatibility settings for each decoder.

Remediate safely

  • Replace native object deserialization with a data-only format and explicit schema validation.
  • If replacement is not immediate, use a safe decoder with a minimal type allowlist and disable polymorphic or executable hooks.
  • Update the affected library and add inert tests for unknown types, extra fields, malformed nesting, and unsigned data.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.