Who is affected
Cisco BroadWorks is a unified communications platform used by service providers and enterprises for voice, video and messaging services. The vulnerability affects BroadWorks deployments where XML parsing is used to handle external entity references. The record does not specify which versions or deployment configurations are vulnerable, nor whether on-premises, cloud or hybrid configurations are equally affected.
How to check whether this touches you
- Inventory your communications infrastructure: confirm whether you operate or depend on Cisco BroadWorks in any form (hosted, on-premises, or managed service).
- Establish network exposure: determine whether your BroadWorks administration interfaces or API endpoints are reachable from untrusted networks or the internet.
- Confirm running version and build: contact your Cisco support representative or check system administration dashboards for the precise Cisco BroadWorks release currently deployed. Version alone is a signal; patch status requires vendor confirmation.
- Review current configuration: identify which BroadWorks XML-processing features and integrations are active in your environment.
What to do
- Immediately contact Cisco support to obtain the authoritative patch or mitigation guidance for your specific BroadWorks version and deployment model.
- Whilst awaiting a patch, restrict network access to BroadWorks XML parsing endpoints to trusted internal networks only; disable external API access if operationally feasible.
- Enable audit logging on all BroadWorks XML configuration reads and uploads; configure log retention for at least 90 days.
- If running BroadWorks as a cloud or managed service, request written confirmation from your provider that mitigations or patches have been applied; document the date and version.
- Escalate to your security team if mitigations cannot be deployed within the federal remediation window (2026-11-24) or if your deployment cannot be isolated from untrusted networks.
If you find you were exposed
Exploitation of XML entity vulnerabilities typically occurs without obvious application-layer signatures, so hunting will depend on reconstructing XML requests from access logs or proxy records predating your remediation. Review logs for unusual attempts to read external entities, file inclusion patterns, or requests to configuration endpoints from unexpected sources. Retention constraints mean you may only capture a subset of the exposure window; work backwards from the vulnerability announcement date to the earliest logs available.