Affects widely used Cisco Unified Communications products; high CVSS (8.8) and can disrupt enterprise voice and collaboration services across organizations.
CVE-2026-76478
Access-control flaws in Cisco Unified Communications allow unauthorized access/control.
Is CVE-2026-76478 being exploited?
Not confirmed. CVE-2026-76478 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-76478?
CVE-2026-76478 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76478?
Yes. A fix has been recorded for CVE-2026-76478. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76478 affect?
CVE-2026-76478 affects Cisco Emergency Responder, Cisco Prime Collaboration Deployment, Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76478?
Install Cisco hardening updates immediately; restrict admin access and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Improper access control enabling unauthorized access to UC functions, possible privilege escalation, data exposure, and service disruption.
Immediate action required
- affected14
- affected14SU1
- affected14SU2
- affected14SU3
- affected14SU3a
- affected15
- affected15SU1
- affected15SU1a
- affected14SU4
- affected15SU2
- affected15SU3
- affected14SU5
- affected15SU4
- affected14SU6
- affected14
- affected14SU1
- affected14SU2
- affected14SU3
- affected15
- affected15SU1
- affected14SU4
- affected14SU4a
- affected15SU1a
- affected15SU2
- affected15.0.1.13010-1
- affected15.0.1.13011-1
- affected15.0.1.13012-1
- affected15.0.1.13013-1
- affected15.0.1.13014-1
- affected15.0.1.13015-1
- affected15.0.1.13016-1
- affected15.0.1.13017-1
- affected15SU3a
- affected14SU5
- affected15SU4
- affected15SU4a
- affected14SU6
- affected14
- affected14SU1
- affected14SU2
- affected14SU2a
- affected14SU3
- affected15
- affected15SU1
- affected14SU4
- affected15SU2
- affected15SU3
- affected14SU5
- affected15SU4
- affected14SU6
- affected14
- affected14SU1
- affected14SU2
- affected14SU3
- affected14SU3a
- affected15
- affected15SU1
- affected14SU4
- affected15SU2
- affected15SU3
- affected14SU5
- affected15SU4
- affected14SU6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.