Critical PHP Security Vulnerabilities: Action Required for FreePBX and PBXact

On October 21, 2026, the PHP development team disclosed two critical security vulnerabilities (CVE-2026-109618 and CVE-2026-109619) that could allow unauthorized remote code execution on affected systems. These vulnerabilities affect PHP, a third-party technology used in the underlying infrastructure of FreePBX and PBXact.

We know unexpected security updates and migrations can be disruptive, and we’re here to help you navigate the next steps. :person_tipping_hand:

:police_car_light: Immediate Action Recommended:

  • FreePBX 17 / PBXact 17: Apply the latest PHP security updates by following the standard system software update procedures outlined in our documentation. Verify that the updated packages have been installed.

  • FreePBX 16 / PBXact 16 and earlier: We strongly recommend planning your migration to version 17 as soon as possible. As a temporary measure, we are offering a patched PHP 7.4 for testing in FreePBX/PBXact 16, while evaluating additional measures to reduce exposure for customers who cannot migrate immediately.

Important: Plan your migration to Version 17

Migrating to version 17 requires some planning, as it is not an in-place upgrade. It requires a fresh installation and migration of your existing configurations using the Backup and Restore module. Ensure your new installation has received the latest security updates before placing it into production.

Protect your system in the meantime

Until your system is updated or migrated, restrict access to the web management interface to trusted networks. These measures help reduce exposure but do not eliminate the risk.

Further Assistance

If you’re running version 16, but unable to: migrate to version 17, test the patched PHP 7.4, or restrict access to your systems; Sangoma and its partners may be able to help you explore additional security options for your legacy system. Contact Sangoma Sales to discuss your options.

Additional Resources

We recognize that this may create additional work for our customers and partners, and we appreciate your efforts to keep your systems secure. Our team continues to work on practical solutions and is here to help you navigate the next steps.

Sangoma Open Source Team :heart: :frog:

Additional mitigation ideas:

/etc/php.d/zzz-php2shell-stopgaps.ini

You might consider adding this file to your system and then restarting Apache. It includes some suggestions from php.net news items including the front page today, and elsewhere:

; still recommended upstream as of October 23
; even if you applied the October 21 patches
session.upload_progress.enabled=0
; careful on busy systems this could slow performance
; but many FreePBX systems are gentle on the Web UI
opcache.enable=0
; warning - setting this can lead to crashes
; should not be needed on patched systems
;memory_limit=-1

On v17, if you haven’t updated Debian packages for a while, and now when running apt update you are seeing some GPG key errors like this:

Get:20 http://deb.debian.org/debian bookworm/main Translation-en [6,107 kB]                                                                       
Get:21 http://deb.debian.org/debian bookworm/non-free-firmware amd64 Packages [6,368 B]                                                           
Fetched 40.7 MB in 9s (4,593 kB/s)                                                                                                                
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
304 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'http://ftp.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.12' to '12.15'
N: Repository 'http://deb.debian.org/debian bookworm InRelease' changed its 'Version' value from '12.12' to '12.15'
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.freepbx.org/freepbx17-prod bookworm InRelease: The following signatures were invalid: EXPKEYSIG C4DFE68FCE6DE186 Aptly <[email protected]>
W: Failed to fetch http://deb.freepbx.org/freepbx17-prod/dists/bookworm/InRelease  The following signatures were invalid: EXPKEYSIG C4DFE68FCE6DE186 Aptly <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.

…then please run fwconsole ma updateall and, after that, try again with the apt update command.

All supported FreePBX versions have updated production PHP fixes in place.

v17 - We relied on upstream Debian package maintainers - thank you! - which was available within a day or so of the initial publication of the vulnerability.

v16 - We manually built updated PHP 7.4.33-31 RPMs, got them into testing within a day or so, and they entered production last week. Running yum update on the CLI, then restart of processes and/or reboot, is now sufficient to apply the change. The update may (possibly) be done via the GUI as well if that is where you manage your system packages.

I upgraded PHP from 8.2.29 to 8.2.35. When I enter PHP -V on the system CLI, I get:
PHP 8.2.35 (cli) (built: Oct 21 2026 06:29:51) (NTS).
However the warning to upgrade PHP in FreePBX persists. It tells me that I am running PHP8.2.29 and that I need to upgrade to 8.2.35.
How do I fix this?

Running processes, like Apache, will continue to use the old library – they need to be restarted to pick up the fix. If you already did that, rebooted, etc., then closing out the warnings and reloading the Dashboard should be sufficient to keep the messages from re-appearing.