Applies to: Self-managed 3CX on Linux and Windows (on-premise or in your own cloud), including Multi Company systems you or your partner run. Hosted by 3CX and 3CX SMB systems are updated by 3CX.
Two critical security flaws were made public in NGINX on 18 November. NGINX is the web server built into every 3CX that serves the Web Client and Admin Console. We have released an update that includes the fixed NGINX version.
Hosted by 3CX or 3CX SMB? 3CX updated your system on 20 November. No action is required.
If you manage your own PBX, read on to learn how to update and how to check that your PBX has the fix.
Who Does This Apply To?
Self-managed 3CX PBXs on Linux and Windows running V20 Update 10 or Update 9, including Multi Company systems run by you or your partner. Update to the latest Update 10 build as soon as possible.
The flaws are in NGINX itself, the web server used by more than 225 million websites, not in 3CX code. F5, the company behind NGINX, released the fix on 18 November and recommends that everyone update. 3CX tested the new NGINX version and released it in a 3CX update on 20 November.
If you are running a 3CX Hosted PBX or a 3CX SMB system: no action required!
How to Update
- Log in to the Admin Console.
- Go to Updates.
- Install V20 Update 10, build 20.0.10.1801.
PBXs on Update 9 go straight to build 1801. If automatic updates are turned on, your PBX installs the update by itself in its scheduled update window. For the full list of changes, see the V20 change log.
How to Check You Have the Fix
The Admin Console Dashboard shows version 20.0.10.1801 or higher.
Running 3CX on Windows?
Windows systems get the same update, build 20.0.10.1801. You can keep using Windows, but with the number of security releases we are seeing, now is the time to lock your Windows server down: keep Windows Update on, allow only the ports 3CX needs through the firewall, and restrict remote access to the server.
Until you have installed the update, limit who can reach the 3CX web port (HTTPS): where you can, allow it only from your office, your VPN or other known IP addresses.
What Happened?
On 18 November F5 released NGINX 1.30.7 and published two critical vulnerabilities, CVE-2026-123633 and CVE-2026-123007 (F5 assigned both nginx HTTP/2 vulnerabilities the same base scores: 9.2/10 (Critical) under CVSS v4.0 and 8.1/10 (High) under CVSS v3.1. CVE-2026-123007 · CVE-2026-123633). Both affect NGINX servers that use HTTP/2, and 3CX uses HTTP/2.
3CX V20 Update 10 build 20.0.10.1801 includes NGINX 1.30.7. 3CX updated all Hosted by 3CX and 3CX SMB systems on 20 November.
3CX builds and tests its own NGINX packages directly from the official NGINX source. This allows us to release security fixes independently of Debian's update schedule.
3CX systems on build 20.0.10.1801 are already protected.
We also released the latest Debian security updates through the 3CX repository: PBX security updates.
Consider 3CX Hosted
If you'd rather not manage server security yourself, Hosted by 3CX takes care of it for you. As we've highlighted before, security threats are constantly evolving, making regular monitoring and timely updates essential. If you don't have the time or resources to manage this, we recommend considering a move to 3CX Hosted.
We also recommend subscribing to 3CX news through our blog to stay informed about important updates. Critical system, security and license-related notifications are automatically sent to the email address linked to your 3CX installation. These emails are mandatory and cannot be unsubscribed from. Make sure your mail server, spam filters and security software are not blocking emails from 3CX or sending them to your junk folder.
You can also stay up to date with the latest announcements through our Partner and Customer Forums, or follow us on X and LinkedIn.


