Check these three things.
-
System owner: confirm BroadWorks Application Server, Profile Server, Xtended Services Platform and Application Delivery Platform systems run release RI.2026.07 or later.
What to confirm
- Record for each server in these four Cisco BroadWorks products:
- The product.
- The installed release.
- The record source and date.
- Releases earlier than RI.2026.07 are affected regardless of device configuration. No setting makes an earlier release safe.
- Cisco names RI.2026.07 as the first fixed release for all four products. Cisco lists no workaround.
- If a provider runs BroadWorks for you, ask the provider for the same release record.
- Record for each server in these four Cisco BroadWorks products:
-
Network owner: confirm which networks can reach the OCI-P service on BroadWorks servers running releases before RI.2026.07.
When the risk applies
- OCI-P (Open Client Interface – Provisioning) is the BroadWorks service that accepts XML provisioning messages. The flaw is triggered by a crafted XML message sent to it.
- The attacker needs no account and no user action.
- For Application Delivery Platform, Cisco's fix table refers to Open Client Server (OCS) and OCIOverSoap.
- Internet reachability of OCI-P is unknown until checked. A network attack rating alone does not show the service faces the internet.
- Records needed:
- Firewall and access rules in front of each affected server.
- The partner, customer or internet ranges allowed to connect to OCI-P.
- The date of each record.
- Narrowing access is not a Cisco-documented fix. It does not replace the update.
-
Security owner: check records from servers that ran releases before RI.2026.07 for signs that files were read through OCI-P.
What the records can show
- Records to review, where retained:
- OCI-P request logs, especially XML messages that declare external entities.
- Outbound connections from these servers to unfamiliar destinations.
- Cisco's advisory title calls this an out-of-band blind flaw. That term usually means file content leaves through a separate connection rather than in the reply.
- Cover the whole period each server ran an affected release with OCI-P reachable. An update does not show whether files were read earlier.
- Missing or short-lived logs leave harm unknown. They do not show safety.
- Records to review, where retained:
If any affected server runs a release before RI.2026.07, update it now. Cisco lists no workaround, and CISA lists the flaw as exploited.
Do Now
- System owner: update affected BroadWorks servers to release RI.2026.07 or later.
What to ask
- Applies to Application Server, Profile Server, Xtended Services Platform and Application Delivery Platform systems.
- Completion evidence for each server:
- The server name.
- The release installed after the update.
- The date and record source.
- If a provider runs BroadWorks for you, ask the provider for the same evidence.
- Security owner: start incident response if records show files read through OCI-P.
What to ask
- Triggers to escalate:
- OCI-P XML messages that declare external entities.
- Unexplained outbound connections from affected servers during the exposure period.
- Response scope:
- The servers involved.
- The period each ran an affected release.
- The files the BroadWorks user could read.
- An update does not end the investigation.
- Triggers to escalate:
Do Next
- Security owner: list sensitive files the BroadWorks user could read on servers exposed before the update.
What to ask
- This shows what an attacker could have seen. Include:
- BroadWorks configuration files.
- Other files readable by the BroadWorks user.
- If incident response is open, use the list to decide what must change.
- This shows what an attacker could have seen. Include:
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported finding
OCI XML parser external entity file read (CWE-611)
Original advisory →- Required conditions
- Cisco BroadWorks Application Delivery Platform, Application Server, Profile Server or Xtended Services Platform on a release earlier than RI.2026.07.
- The attacker can send a crafted XML message to the Open Client Interface – Provisioning (OCI-P) service.
- No sign-in or user interaction is needed (CVSS PR:N, UI:N).
- Cisco states the flaw applies regardless of device configuration.
- Reported outcome
- The OCI XML parser allows external entity resolution by default. An XML external entity is a reference inside a message that tells the parser to load content from a file or another location.
- A successful attack lets the attacker view sensitive files from the filesystem with the privileges of the Cisco BroadWorks user.
- Cisco titles the flaw an out-of-band blind XML external entity injection.
- The CVSS vector records high confidentiality impact and no integrity or availability impact.
- CISA's SSVC enrichment records exploitation as active, automatable as yes and technical impact as partial.
Fix guidance
- Cisco: first fixed release RI.2026.07 for all four affected products. No workarounds.
- Fix map:
- Application Delivery Platform: earlier than RI.2026.07 affected, fixed in RI.2026.07. Cisco's table notes Open Client Server (OCS) and OCIOverSoap.
- Application Server: earlier than RI.2026.07 affected, fixed in RI.2026.07.
- Profile Server: earlier than RI.2026.07 affected, fixed in RI.2026.07.
- Xtended Services Platform: earlier than RI.2026.07 affected, fixed in RI.2026.07.
- The CVE record lists the affected version as "N/A". Cisco's advisory gives the release ranges above.
- Cisco first published the advisory on August 19, 2026. An update closes the flaw going forward. It does not show whether files were read before.
- Exploitation status:
- CISA added the flaw to KEV on November 10, 2026, with a due date of November 24, 2026 under BOD 26-04.
- KEV lists known ransomware campaign use as Unknown.
- Cisco's revision 1.2 (November 13, 2026) states Cisco does not have direct evidence of active exploitation.
What IntegrityLab.ai can check
- IntegrityLab.ai discovery records reachable web services within an authorized target list and budget:
- The HTTP status.
- The page title.
- The server banner.
- No current IntegrityLab.ai check identifies:
- Cisco BroadWorks or its release.
- The OCI-P service.
- CVE-2026-20320.
- Signs that files were read.
- A recorded web service or banner can point the Network owner to a server to review. It does not establish the product, the release, OCI-P reachability or this flaw. A missing observation does not establish safety.