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.