CVE-2026-20045: Cisco Unified Communications Products Code Injection Vulnerability

P0 — ACT NOWCISA KEVRANSOMWARE: UNKNOWNFORENSIC TRIAGE: NO

Quick Answer

CVE-2026-20045 permits unauthenticated HTTP requests to the management interface to obtain operating-system user access and then root. Cisco lists Unified CM, Session Management Edition, IM and Presence, Unity Connection and Webex Calling Dedicated Instance regardless of configuration. Preserve management and host evidence, then use the product-specific update or COP below. Cisco reports attempted exploitation; CISA independently records known exploitation.

Fix Or Immediate Action

What to do now: Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2026-20045 to KEV on 2026-01-21.

Open the live Cisco advisory

Evidence check: Vendor evidence and unresolved limits are described below. CISA KEV catalog 2026.10.02 was checked October 2. Catalog additions, vendor publication dates and update releases are separate events. No exploit, installation or recovery test is claimed.

Context

Scope And Impact In Plain Language

Who should check: Anyone who manages Cisco Unified Communications Manager.

When this applies: Only when the exact product, version, and required configuration match the live vendor advisory. Owning the product family alone does not mean the device is vulnerable.

What could happen: A successful attacker may be able to run attacker-chosen commands or software on the affected system, subject to the access and configuration requirements in the advisory.

Not sure? Find the product name and version in the device or application, then compare them with the affected-products section of the linked vendor notice.

Status At A Glance

Product scopeUnified CM, Unified CM SME, Unified CM IM and Presence, Unity Connection, Webex Calling Dedicated Instance
CVECVE-2026-20045
TechGeeks response tierP0 — confirm an exact match and act now
CISA KEV added2026-01-21
Vendor severityCritical (Cisco advisory rating; distinct from numerical CVSS band).
CVSS8.2 (Cisco CVSS v3.1 base).
Ransomware fieldUnknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage fieldNo in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWECWE-94
Federal remediation date2026-02-11 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Cisco Unified Communications Products Code Injection Vulnerability. Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unity Connection, and Cisco Webex Calling Dedicated Instance contain a code injection vulnerability that could allow the attacker to obtain user-level access to the underlying operating system and then elevate privileges to root. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unity Connection, and Cisco Webex Calling Dedicated Instance contain a code injection vulnerability that could allow the attacker to obtain user-level access to the underlying operating system and then elevate privileges to root.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

  1. Confirm. Inventory every Unified Communications Manager asset and record its exact version, patch level, role, relevant configuration, and exposure.
  2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
  3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Cisco advisory.
  4. Remediate. Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2026-20045 to KEV on 2026-01-21.
  5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
  6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Permanent Fix

Use the package README for the exact product/version and a supported compatible upgrade path. The advisory's scheduled release date does not verify that a download is available.

Product / releaseCisco remedy
Unified CM / SME / IM and Presence / Webex Dedicated Instance 12.5Migrate to a fixed release.
Same products 1414SU5 or ciscocm.CSCwr21851_Remote_Code_Execution_v1.zip
Same products 1515SU4 or ciscocm.CSCwr21851_Remote_Code_Execution_v1.zip
Unity Connection 12.5Migrate to a fixed release.
Unity Connection 1414SU5 or ciscocm.cuc.CSCwr29208_C0266-v2.zip
Unity Connection 1515SU4 (advisory date: March 2026; download not verified) or ciscocm.cuc.CSCwr29208_C0266-v2.zip

Workaround Or Temporary Mitigation

Cisco lists no workaround. Restrict the management interface to trusted sources while preparing the correct product-specific fix; network filtering is not removal of the injection flaw or evidence of eradication.

Important boundary: A workaround, access restriction, or provider-side control may reduce risk while the update is prepared, but it does not necessarily remove vulnerable code or erase an earlier compromise. Install the vendor-approved update when one is available.

Investigation And Recovery

CISA's KEV record does not mark this entry for forensic triage. That field is not proof of a clean system; consult the vendor advisory for indicators and recovery guidance.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Cisco says it is aware of attempted exploitation in the wild. CISA separately lists this CVE as known exploited. Neither statement establishes that an individual communications system is clean after an update.

CISA statement: CVE-2026-20045 was added to KEV on 2026-01-21. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

References

Wrap-Up

Record whether CVE-2026-20045 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.