CVE-2026-76473
As part of Cisco's ongoing commitment to proactive security and product quality, engineering teams for Cisco Emergency Responder, Cisco Prime Collaboration Dep…
Auswirkung
As part of Cisco's ongoing commitment to proactive security and product quality, engineering teams for Cisco Emergency Responder, Cisco Prime Collaboration Deployment, Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), and Cisco Unity Connection have conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76473 are related to issues concerning improper neutralization of special elements in output used by a downstream component that are grouped under the Common Weakness Enumeration (CWE) Class CWE-74.
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, ohne Zutun eines Nutzers. Bei Erfolg: hohes Risiko, dass Daten ausgelesen werden, hohes Risiko, dass Daten oder Systeme verändert werden, hohes Risiko für Ausfälle.
Betroffene Produkte · Cisco
| Produkt | Betroffene Versionen |
|---|---|
| Cisco Emergency Responder | Versionen 14SU6, 15, 14SU5, 14SU4, 14SU3, 14 |
| Cisco Unified Communications Manager | Versionen 15SU2, 15.0.1.13015-1, 15.0.1.13012-1, 15.0.1.13010-1, 15SU3a, 15.0.1.13013-1 |
| Cisco Unified Communications Manager IM and Presence Service | Versionen 15SU3, 15SU1, 14SU2, 15, 15SU4, 14SU6 |
| Cisco Unity Connection | Versionen 14SU3a, 15SU4, 14SU6, 14SU2, 15SU1, 14SU3 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-voice-hardening-twgbH9e3
- https://github.com/advisories/GHSA-g392-rjcx-4cp4
- https://nvd.nist.gov/vuln/detail/CVE-2026-76473
- https://www.cve.org/Media/News/item/blog/2026/06/16/Preserving-Vulnerability-Level-Identification