CISA added CVE-2026-20320 to the Known Exploited Vulnerabilities catalog on Tuesday. Cisco BroadWorks, CVSS 7.5 (AV:N/AC:L/PR:N/UI:N), unauthenticated. Cisco patched it in August. So somebody had a quarter to read an advisory and a few bad actors had the same quarter to read the same one.
The bug is an XML External Entity flaw, and I want you to sit with that acronym for a second. XXE. It was on the OWASP list when some of you were in grade school. Per Cisco’s advisory, the OCI (Open Client Interface) XML parser handles “XML entries” improperly “because external entity resolution being allowed by default.” Send a crafted XML message to the OCI-P provisioning service and you can read files off the filesystem with the privileges of the BroadWorks user. Confidentiality only, per the vector: C:H/I:N/A:N. Cisco’s advisory is titled “out-of-band blind,” so you don’t even get the file in the response, which is a design choice by the attacker’s tooling and not a comfort to you.
Allowed by default. Every XML library I’ve touched has had a switch for this since the early 2000s, and the sane setting has been “off” for about as long. Somebody wrote a parser, left the doctype machinery wired up, and shipped it in a carrier-grade telephony platform. Telcos run this stuff. That’s the whole story of the industry in one config default.
Affected, per Cisco: Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform, “regardless of device configuration.” No workarounds. Cisco’s words, not mine: “There are no workarounds that address this vulnerability.” The fixed releases are in the Fixed Software table in the advisory, and I’m not going to paste version numbers from memory into a patch notice. Read the table.
Now the part that moved it onto the KEV list. BleepingComputer reports that Malbear Labs says a Chinese-speaking actor used the flaw, with a jailbroken DeepSeek Flash model driving the work, against a European telecom provider and thirteen organizations hosted on its infrastructure. Per that report, a crafted OCI request to port 2208 on the XSP host got back the system identity private key, three SSL credential sets, and three more private keys. The system identity key is what BroadWorks components use to authenticate to each other, so holding it means impersonating the XSP. I can’t verify Malbear’s telemetry from here, and I’m relaying it as reported. The AI angle is the headline bait. The interesting part is the unglamorous one: a file-read bug turned into keys to the kingdom because the keys were sitting on the same box.
One more thing. Cisco’s advisory still says its PSIRT “is not aware of any public announcements or malicious use.” That text is stale now. Advisories are snapshots. Check the date on whatever you’re reading, including this.
What to do:
- Inventory BroadWorks. If you’re a carrier or an MSP reselling cloud PBX, you know whether you run it. If you don’t know, ask somebody who does.
- Upgrade to the fixed release from Cisco’s table. CISA’s deadline for federal civilian agencies is November 24 under BOD 26-04, and it urges everyone else to treat KEV entries the same way.
- Don’t expose OCI-P to the internet. Provisioning interfaces belong on a management network behind an ACL, not on a port anyone can probe.
- If you were exposed and unpatched since August, assume the files the BroadWorks user could read are gone. Rotate the system identity key, the TLS keys and certificates, and whatever credentials sit in config files. Patching closes the door; it doesn’t un-steal anything.
Parsers eating hostile input remain the oldest source of CVEs there is. Compare the Cisco IOS XE bug still being scanned years after its fix; patch lag is the real vulnerability. More in the kernel and security hub. Go patch.
