Products and stacks · Firewalls, appliances and IT tools
PHP2Shell in OPNsense: is it affected and how to fix it
How to check the PHP version OPNsense uses
Run the command for your setup. A version at or above 8.2.35, 8.3.36, 8.4.27 or 8.5.12 in its branch is fixed; older branches are fixed only by a vendor build that says so.
opnsense-version
php -vThe command-line php can differ from the PHP that serves the site. To be sure, check the web SAPI (a temporary phpinfo() page behind authentication, or the panel's PHP settings) and remove it afterwards. Our version checker compares a version number for you.
🔎 Got a version number? Paste it into the PHP2Shell checker →
How to fix PHP2Shell in OPNsense
- Go to System → Firmware → Updates, install 26.7.7 (or BE 26.4.2p3), then reboot or restart the web GUI.
- Install the vendor's fixed release or packages listed above.
- Restart every PHP process (PHP-FPM pools, Apache with mod_php, LiteSpeed lsphp, queue workers); a running process keeps the old PHP in memory.
- Confirm the running version again with the check commands.
Prefer to let an AI agent do the checks? Check if you are affected · Fix with an AI agent
If you cannot patch yet
- Set
session.upload_progress.enabled = 0where applications cannot override it (php.ini,php_admin_valuein the FPM pool or Apache config), and restart PHP. - On PHP 8.5, set
fatal_error_backtraces = 0. - PHP's interim advice also covers
memory_limitand a lowpost_max_size; follow the remediation page exactly, because these settings only reduce some paths. - Restrict access (VPN, IP allowlist) or take the service offline if it runs PHP 8.1 or older with no vendor backport. WAF rules help but are not a fix.
FAQ
Is OPNsense affected by PHP2Shell?
Affected until you install the vendor's fixed release. OPNsense 26.7.7 ships PHP 8.5.12 and Business Edition 26.4.2p3 ships PHP 8.3.36, both announced as PHP2Shell fixes.
Does updating OPNsense itself fix CVE-2026-109618 and CVE-2026-109619?
Only if the update contains fixed PHP. PHP2Shell is a flaw in the PHP interpreter, so what matters is the PHP that OPNsense runs on. Check the version after updating.
Which PHP versions fix PHP2Shell?
PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, released 21 October 2026. PHP 8.1 and older get no release from the PHP project; only vendor builds with a backport (or a self-built source patch for 7.4, 8.0 and 8.1) fix them.
What if OPNsense has no fix yet?
Keep its PHP-based web interface off the internet (VPN or IP allowlist), apply PHP's interim settings such as disabling session upload progress, and install the vendor update as soon as it ships. Interim settings reduce risk but are not a fix.
Related products
- pfSense (Netgate)Vendor fix available
- FreePBX and PBXactAffected, no fix yet
- Nagios XIPatch your OS / host PHP
- Zabbix frontendPatch your OS / host PHP
- GLPIVendor fix available
- Palo Alto Networks PAN-OS and PanoramaAffected, no fix yet
← All products that bundle PHP
See also: Remediation by platform · Affected versions · Vendor status
Sources
- OPNsense forum announcements
- Mallory: PHP2Shell – am I affected? (product table)
- PHP advisory GHSA-w8hw-w9fx-j79w
- PHP advisory GHSA-6wmf-4rv5-p3rp
Outbound links leave this site. We do not host exploit code.
Unofficial summary of public sources. This site is not affiliated with the vendor or the PHP project and hosts no exploit code.