If you manage your own 3CX on Linux or Windows, install 3CX’s NGINX security update now. NGINX is the web server inside every 3CX that serves the Web Client and Admin Console, and two critical flaws in it were made public on November 18.
If 3CX hosts your system, or you run 3CX SMB, 3CX says it updates those systems itself. You have nothing to install.
What happened
On November 18, F5 released fixes for a group of NGINX flaws that researchers call NGINX2Root. The two that matter most for a 3CX server are CVE-2026-123633 and CVE-2026-123007.
Wiz, which reported them, rates both critical at 9.2 (CVSS 4.0). Both are in NGINX’s HTTP/2 code, and Wiz says both “require HTTP/2 to be enabled on the affected NGINX server.” CVE-2026-123007 affects NGINX versions back to 1.9.5 from 2015.
Upstream NGINX fixed them in 1.30.7 (stable) and 1.31.9 (mainline). Three more critical flaws were fixed at the same time, in the HTTP/3, resolver and mail proxy code.
How serious is it right now
As of November 19, Tenable reported no evidence of these flaws being exploited in the wild. They were not on CISA’s Known Exploited Vulnerabilities list.
A public proof of concept exists for CVE-2026-123007. Tenable describes it as constrained: it needs a specific x86-64 code path, around 128 GB of HTTP/2 traffic and a way around memory protections. Censys estimated about nine million NGINX services were running an affected version with HTTP/2 on.
A 3CX Admin Console and Web Client are often reachable from the internet so that remote users and mobile apps can connect. That is why this is worth doing today rather than at your next maintenance window.
Who needs to act
| Your 3CX | What to do |
|---|---|
| Self-managed on Linux, on premises or in your own cloud | Install the update |
| Self-managed on Windows | Install the update |
| Multi Company systems you manage | Install the update |
| Hosted by 3CX | Nothing; 3CX updates it |
| 3CX SMB | Nothing; 3CX updates it |
What to do
- Read 3CX’s announcement and note the build number it names.
- In the Admin Console, open System > Updates. That is where 3CX delivered its last NGINX hotfix in June 2026.
- Install the security update, ideally outside business hours.
- Confirm the new build shows in the Admin Console, then log in to the Web Client and place a test call.
- If you turned off HTTP/2 or restricted port 443 as a stopgap, undo it once you are patched. Wiz advises turning HTTP/2 back on after upgrading.
- Repeat for every self-managed system, including Multi Company systems and customer systems you support.
What to watch out for
3CX ships its own NGINX. Since June 2026, 3CX embeds NGINX in its own build rather than waiting for Debian’s package. On Linux, ordinary Debian updates alone are not the fix; the 3CX update is.
A reload is not enough on any NGINX. Xint, which named NGINX2Root, notes that a configuration reload does not replace the running program. If you run other NGINX servers yourself, restart them after upgrading.
Stopgaps have side effects. Before the fix, some admins on the 3CX forum turned off HTTP/2 or limited port 443 to trusted addresses. One customer reported that limiting port 443 kept mobile app calls and push working, but presence and the queue button stopped working.
A separate Linux kernel issue is still open. Xint reports an unpatched Linux kernel SCTP flaw, with no CVE as of November 19, that can be chained with CVE-2026-123007. Xint advises blocking the SCTP module on hosts that do not use it until a kernel fix exists. Check with 3CX before changing kernel modules on a 3CX server.
If you would like help
VoIPTools is a 3CX Platinum Partner with 24/7 support from the USA, India and the Philippines, and we offer managed hosting for 3CX. If you would rather not patch systems yourself, book a call with our team.
Sources
- 3CX VoIP Blog (listing of Critical NGINX Security Update, Nov 20, 2026)
- Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 (Wiz)
- NGINX2Root FAQ: Five vulnerabilities in NGINX (Tenable)
- Security Update: HTTP/2 BOMB Vulnerability Mitigation (3CX, June 2026)
- NGINX CVE, 3CX forum thread
- nginx CVE-2026-123007, 3CX forum thread