As part of Cisco's ongoing commitment to proactive security and product quality,…

Cisco Emergency Responder

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…

Do this now

Apply Cisco's fix to Emergency Responder and the listed Unified Communications products.

Still cooking for Cisco Emergency Responder.

First seen: 27 Oct 2026
Last update: 27 Oct 2026, 12:17 UTC
Identifiers: CVE-2026-76473
CVE-2026-76474
CVE-2026-76475
CVSS: 9.8
Source: news
On the menu as: VPN & firewalls

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## As part of Cisco's ongoing commitment to proactive security and product quality,…
Severity: critical. Patch status: patched.
Affected: Cisco Emergency Responder
Ids: CVE-2026-76473, CVE-2026-76474, CVE-2026-76475

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 &amp; Presence Service (Unified CM IM&amp;P), Cisco Unified Communications…

## Steps
1. This touches infrastructure (vpn-edge). Look in terraform, ansible, cloud-init, Dockerfiles and docs for the product and version we run. If it isn't in the repo, say so and list what a human should check on the box.
2. Fix by release line: Cisco Emergency Responder: 14.x → migrate to a fixed release.

## Fix by release line
| Line | State | Fix | Until then |
|---|---|---|---|
| Cisco Emergency Responder 14.x | migrate | migrate to a fixed release | Cisco has released software updates that address these vulnerabilities |

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2026-76473") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://nvd.nist.gov/vuln/detail/CVE-2026-76475 https://nvd.nist.gov/vuln/detail/CVE-2026-76474 https://nvd.nist.gov/vuln/detail/CVE-2026-76473 https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-voice-hardening-twgbH9e3
https://pwned.coffee/i/as-part-of-cisco-s-ongoing-commitment-to-proactive-secur-cve-2026-76473

Timeline

27 Oct 2026, 12:17 UTC
Fix status: unknown → patched.
27 Oct 2026
First reported.

Receipt

Exploitation: No known exploitation
Fix by release line: Product Affected Fixed in Source
Cisco Emergency Responder 14 to now migrate to a fixed release Vendor advisory checked 27 Oct
Score: CVSS 9.8 (critical). CVSS 3.1 9.8 (CNA cisco) for CVE-2026-76473
Last checked: 27 Oct 2026, 12:17 UTC

Product	Affected	Fixed in	Source
Cisco Emergency Responder	14 to now	migrate to a fixed release	Vendor advisory checked 27 Oct

Sources: KEV – CVE record ✓ Vendor ✓

Sources

Wrong fix version, or a source we missed? Send it back to chef@pwned.coffee with the source, and we'll correct it here.

Totalone very hot coffee