Exploited XXE flaw in Cisco BroadWorks lets unauthenticated attackers read configuration data
CISA added CVE-2026-20320, an XML external entity flaw in Cisco BroadWorks, to its Known Exploited Vulnerabilities catalogue on 10 November 2026. Organisations running BroadWorks are affected, and US federal agencies must remediate by 24 November 2026.
What to do now
- Product
- Cisco BroadWorks
- Affected versions
- —
- CVE
- CVE-2026-20320
The US Cybersecurity and Infrastructure Security Agency (CISA) has listed CVE-2026-20320, a vulnerability in Cisco BroadWorks, in its Known Exploited Vulnerabilities catalogue. Inclusion in that list means CISA has evidence the flaw is being exploited in the wild.
The weakness is an XML external entity issue (CWE-611): BroadWorks does not properly restrict references to external entities when it processes XML input. A remote attacker who has no credentials can abuse this to read sensitive configuration information from an affected system.
Cisco has published a dedicated security advisory (cisco-sa-bworks-xxe-uwUd7CEt). The source does not list affected or fixed BroadWorks versions, so administrators need to check the vendor advisory itself to determine which updates or mitigations apply to their deployment.
For US federal agencies, CISA has set a deadline of 24 November 2026 under Binding Operational Directive 26-04, which prioritises security updates based on risk. Where mitigations are not available, the directive calls for discontinuing use of the product. According to the source, no forensic triage is required for this entry, and whether the flaw has been used in ransomware campaigns is unknown.
Organisations outside the US federal scope should still treat the listing seriously. Configuration data leaked through this flaw can give an attacker the details needed to move further into a network.
What to do now
- Review Cisco advisory cisco-sa-bworks-xxe-uwUd7CEt and apply the fixes or mitigations it describes for BroadWorks right away.
- Identify any BroadWorks instances reachable from the internet and, as general good practice, limit network access to them until they are remediated.
- Check BroadWorks logs for unusual XML requests coming from unauthenticated sources.
- Treat credentials and secrets stored in the configuration as potentially exposed and plan to rotate them if compromise is suspected.