PHP2Shell (CVE-2026-109618 / CVE-2026-109619) is a critical security problem in PHP itself that lets attackers take over web servers. Every website that runs PHP should be updated to 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer as soon as possible. Read our PHP2Shell check and patch guide.
Disclaimer: before attempting to update the PHP version of your website we would highly recommend that you make a full backup of it, just in case anything goes wrong.
Arch Linux is a rolling release, which means its official repositories always carry the latest stable version of PHP. Updating PHP on Arch, and on distributions built from it such as Manjaro and EndeavourOS, is therefore usually just part of updating the whole system. Antergos, which was also based on Arch, was discontinued in 2019, and EndeavourOS is its closest successor.
Run the command below to see the installed PHP version, and use our free PHP version checker to confirm the version your website is running.
php -v
You can list every installed PHP package, including the separately packaged extensions, with this command:
pacman -Qs php
Arch does not support partial upgrades, so never update PHP on its own with pacman -Sy php. Doing so can leave PHP linked against libraries that do not match the rest of your system. Instead, update everything at once:
sudo pacman -Syu
If PHP is not installed yet, install it together with PHP-FPM and any extensions that are packaged separately, such as GD and Intl:
sudo pacman -S php php-fpm php-gd php-intl
A new PHP release can include changes that break older code, so before running a system update on a live server it is a good idea to read the Arch Linux news page and to test your website on the newer version first.
Manjaro uses the same packages as Arch but holds them back for a short period of testing before releasing them to its stable branch. This means a new PHP version usually arrives on Manjaro a week or two after it reaches Arch. You can update with either sudo pacman -Syu or Manjaro's own tool:
sudo pamac upgrade
On Arch, many common extensions are built into the main php package but are switched off by default. Open /etc/php/php.ini and remove the semicolon from the start of each extension line that your website needs, for example:
extension=mysqli
extension=pdo_mysql
extension=iconv
extension=gd
extension=intl
When pacman updates PHP and you have changed php.ini, it saves the new default file as php.ini.pacnew rather than overwriting yours. Compare the two files after each major update so that you do not miss any new settings.
After the update, restart PHP-FPM and your web server so that they load the new version. Replace nginx with httpd if you use Apache:
sudo systemctl restart php-fpm
sudo systemctl restart nginx
Because the official repositories only offer the newest branch, an older application might stop working after a system update. The Arch User Repository (AUR) contains community packages such as php83 that install an older branch alongside the current one. These packages are not maintained by Arch, so treat them as a short-term measure while you update your code to work with the current version.
If your site shows errors after the upgrade, our guide to common PHP errors after upgrading explains the usual causes. It may also be time to call in a professional to assist, so check out our listings of PHP developers that can help upgrade or maintain your website.