
Decision: Organizations running affected OpenScape 4000 or OpenScape 4000 Manager releases should follow Mitel’s branch-specific update path promptly; the vendor describes two unauthenticated network attack paths with CVSS 3.1 scores of 10.0.[1]
Scope: Product presence alone does not prove exposure. The relevant Platform component, an affected supported release, and attacker reachability under the vendor’s network or adjacent-network conditions all matter.[1]
Reporting cutoff: November 19, 2026, 2:38 a.m. EST / 07:38 UTC.
Affected releases and supported fixes
| Product | Affected supported releases | Vendor path |
|---|---|---|
| OpenScape 4000 | V11 R0.22 through V11 R2.11, and V10 R1.68 and earlier. | Upgrade to V11 R2.14 or later; Mitel also lists PLT HF5 for V11 R1.26 and a patch path for V10 R0.28 through V11 R0.22.[1] |
| OpenScape 4000 Manager | V11 R0.22 through V11 R2.11, plus V10 R1.34, R1.42, R1.54, and R1.68. | Upgrade to V11 R2.14 or later; Mitel also lists PLT HF5 for V11 R1.26 and a patch path for V10 R1.34 through V11 R0.22.[1] |
Do not flatten the branch guidance
Mitel says its product statements cover supported versions only. Follow the exact update instructions for the installed branch rather than treating the bare version number V11 R2.14 as the only remediation route.[1]
What to do now
- Inventory first. From authorized administration records, identify OpenScape 4000 and OpenScape 4000 Manager deployments, the exact product release, and the relevant Platform component before classifying exposure.[1]
- Use the matching supported fix. Apply Mitel’s V11 R2.14-or-later upgrade, the named V11 R1.26 PLT HF5 route, or the applicable V10/V11 patch route for the installed product and branch.[1]
- If updating must wait, restrict access. Mitel says enabling Security Mode restricted access can prevent exploitation as a temporary workaround; use the associated security knowledge-base instructions or an authorized Mitel partner.[1]
- Verify the outcome. Confirm the intended updated build or branch-specific hotfix/patch is active on every managed instance, then recheck the effective restricted-access setting if it was used during rollout.[1]
What remains unknown
The live Mitel advisory establishes affected releases, severity, impact, fixes, and a workaround. It does not state that these flaws are being exploited in the wild, identify victims, or provide assigned CVE numbers; this article makes none of those claims.[1]
Source
- Mitel Product Security Advisory MISA-2026-0013 (initial revision November 18, 2026; accessed November 19, 2026).
