Patch Debian PHP CVE-2026-115560, nginx, and GCP FIPS Now
Debian 13 administrators running PHP or nginx should schedule urgent patching, while Ubuntu 24.04 GCP FIPS administrators need to check update entitlement, external modules, and schedule a reboot
1-minute summary
- Symptom / problem
- PHP มีช่องโหว่ session ที่อาจทำให้รันโค้ดได้ nginx มีช่องโหว่หลายโมดูล ส่วน kernel GCP FIPS ต้องตามสถานะ CVE ที่ข้อมูลยังขัดกัน
- Who should read
- ผู้ใช้แพ็กเกจ Debian 13 php8.4 และ nginx รวมถึง Ubuntu 24.04 ที่ใช้ linux-gcp-fips ผ่าน Ubuntu Pro
- Fix in short
- เทียบแพ็กเกจกับประกาศ อัปเดตจากแหล่งเดิม รีสตาร์ต PHP-FPM หรือ Apache และ nginx ส่วน kernel ต้องรีบูตแล้วตรวจตัวที่รันจริง
I saw the Debian PHP and nginx patch announcements and Ubuntu USN-9174-1 issued on 19 Nov. 2026, so I put the steps together here. After updating packages, restart the processes or reboot so the kernel starts using the new version too. If you have multiple PHP installations, check every one that is running.
Package versions to compare before starting
| Advisory | System and package | Updated version in the advisory |
|---|---|---|
| DSA-6641-1 | Debian 13 trixie / php8.4 | 8.4.28-1~deb13u1 |
| DSA-6642-1 | Debian 13 trixie / nginx | 1.26.3-3+deb13u11 |
| USN-9174-1 | Ubuntu 24.04 / linux-gcp-fips | 6.8.0-1074.82+fips1 |
Compare the full package version, including the distro suffix. Do not rely only on php -v or nginx -v. The kernel version in the table is the one listed in the USN, but the status of one CVE still conflicts with Ubuntu's CVE page, as detailed below.
PHP has additional session vulnerabilities beyond the earlier php2shell flaws
PHP's advisory for CVE-2026-115560 describes a problem where the session writer and reader use different serializers. An attacker may cause PHP to read part of the data as an object. This attack path requires upload progress to be enabled, with the writer using php_binary or php_serialize and the reader using php. Both sides must be able to access the same session. For code execution, the application must also have classes that can be assembled into a gadget chain. Separating FPM pools alone does not automatically separate session storage.
CVE-2026-126714 affects the files session handler. If a file overwrite stops partway through, the tail of the old data may remain. PHP may read this mixed data as an object prepared by the attacker. The attack requires control over session data and the ability to interrupt the write at the right point. Code execution also requires a gadget chain. Disabling upload progress reduces the available attack paths, but there are still cases where the application itself stores user input in the session.
PHP rates both as Critical, CVSS 4.0 = 9.2, with the following published vectors:
| CVE | Vector from PHP |
|---|---|
| CVE-2026-115560 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CVE-2026-126714 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
The value AT:P means the attack also depends on certain conditions. PHP fixed these two CVEs in 8.2.36, 8.3.37, 8.4.28, and 8.5.13, while this Debian advisory covers php8.4 on trixie. These two CVEs are separate from the earlier php2shell flaws.
Debian's tracker for DSA-6641-1 lists 12 CVEs, but the PHP ChangeLog for 8.4.28 lists 14 CVEs. The lists from the two sources differ: the tracker does not list CVE-2026-129481 or CVE-2026-129501. The table below uses the 14 entries from upstream PHP:
| Area fixed | All CVEs in the group |
|---|---|
| Session mismatch / interrupted file write | CVE-2026-115560, CVE-2026-126714 |
| Session shutdown / timezone cache | CVE-2026-129481, CVE-2026-129496 |
| FPM request smuggling / privilege escalation / status XSS | CVE-2026-129289, CVE-2026-129291, CVE-2026-129292 |
| HTTP response headers / URL / PHAR signature | CVE-2026-127960, CVE-2026-128064, CVE-2026-128090 |
| DOM / SOAP / CGI | CVE-2026-129501, CVE-2026-129506, CVE-2026-129538, CVE-2026-15353 |
If you do not use upload progress, set session.upload_progress.enabled=0 in administrator-level configuration before accepting requests. Calling ini_set() in the application is too late. Check serializers and separate session storage for applications that use different formats too. Changing formats requires migrating the existing data or letting it expire, rather than having another decoder read it. PHP still needs to be updated.
Debian's nginx advisory has an additional entry beyond Ubuntu's
DSA-6642-1 lists 9 CVEs for Debian 13, adding CVE-2026-125283 to the 8 CVEs in Ubuntu USN-9159-1. The Ubuntu steps are in the Ubuntu nginx post, while upstream nginx groups the issues by module as follows:
| Area to check | CVE |
|---|---|
| HTTP/2 flow control / use-after-free | CVE-2026-123007, CVE-2026-123633 |
| HTTP/3 / resolver / mail proxy use-after-free | CVE-2026-121810, CVE-2026-123634, CVE-2026-113425 |
| Loop while reading a request body over TLS 1.3 | CVE-2026-118899 |
| stream certificate verification / ssl_preread | CVE-2026-120967, CVE-2026-123640 |
try_files with alias and map variables |
CVE-2026-125283 |
The main one to examine is CVE-2026-123007. This issue causes a heap buffer overflow while handling HTTP/2 flow control and may crash a worker. Code execution requires ASLR to be disabled or the attacker to bypass ASLR. Ubuntu rates it CVSS 3.1 = 8.1 High, with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, while nginx classifies it as major, using different criteria from CVSS.
Debian 12 needs to be checked separately from Debian 13. The tracker for CVE-2026-123007 still shows bookworm as vulnerable, including packages in the security repository. CVE-2026-125283 requires try_files with alias and map variables, together with certain regex captures.
This Ubuntu GCP FIPS advisory covers 24.04
USN-9174-1 covers linux-gcp-fips on Ubuntu 24.04 through Ubuntu Pro / FIPS Updates, listing linux-image-6.8.0-1074-gcp-fips, linux-image-gcp-fips, and linux-image-gcp-fips-6.8 at version 6.8.0-1074.82+fips1. The advisory fixes several subsystems; see the CVE list under References in the full USN. For kernel details, see the cloud and FIPS roundup.
USN-9174-1 references CVE-2026-93221, but Ubuntu's CVE page still shows linux-gcp-fips on 24.04 as Vulnerable. The two pages still conflict. Update according to the USN, but do not consider this CVE fixed yet. Continue checking Ubuntu's status updates.
The advisory says a reboot is required and warns that the ABI has changed. External kernel modules must be rebuilt and reinstalled. Before rebooting, check the headers and DKMS results too. Have console access ready to troubleshoot if the system fails to boot. Installing the new image alone does not change the running kernel.
Update from the existing sources, then make sure everything uses the new versions
- Check the release, package sources, and services actually running
- Prepare data and config backups, schedule downtime, and check FIPS Updates entitlement
- Update after reviewing the package and dependency lists before confirming
- Restart web services or reboot the kernel, then test the application
Check Debian first, showing only packages actually installed, then compare Installed/Candidate against the table:
cat /etc/os-release
dpkg-query -W -f='${binary:Package}\t${Version}\t${db:Status-Status}\n' 'php8.4*' 'libapache2-mod-php8.4' 'nginx*' | awk -F '\t' '$3 == "installed"'
apt-cache policy php8.4-common php8.4-fpm nginx
systemctl list-units --type=service --state=running
This example applies to Debian 13 with php8.4-fpm and nginx installed from Debian. The APT command selects already installed packages for updating. Read the list before confirming. If Candidate is still below the fixed version, check the package repositories first:
sudo apt-get update
sudo apt-get install --only-upgrade '?and(?installed,?name(^php8\.4))' nginx
sudo systemctl restart php8.4-fpm
sudo nginx -t && sudo systemctl restart nginx
If Apache uses mod_php, update libapache2-mod-php8.4 and run sudo apache2ctl configtest before sudo systemctl restart apache2. If Apache connects to FPM, restart FPM too. Any PHP queue workers must also be restarted. For nginx, a reload reads the configuration again; after patching, the new executable must also be started. If you use DirectAdmin or containers, update the PHP and nginx installations that those services run.
For Ubuntu 24.04 GCP FIPS already using this kernel series, check pro status and Candidate first. If the required repository is not enabled yet, follow the FIPS Updates guide during the maintenance window:
uname -r
pro status
sudo apt-get update
apt-cache policy linux-image-gcp-fips linux-image-gcp-fips-6.8
sudo apt-get -s install --only-upgrade linux-image-gcp-fips
# อ่านผลจำลองและตรวจว่า metapackage ตรงกับที่ติดตั้งอยู่ก่อนทำจริง
sudo apt-get install --only-upgrade linux-image-gcp-fips
# ถ้าติดตั้ง DKMS ไว้ ให้ตรวจโมดูลสำหรับ kernel ใหม่
if command -v dkms >/dev/null; then dkms status; fi
# หลังตรวจโมดูลและพร้อมหยุดบริการแล้ว
sudo reboot
If you use a metapackage ending in -6.8, change the name in the command to match. After rebooting, check that uname -r reports 6.8.0-1074-gcp-fips or a newer patched release in the same series, then compare the package version too.
Check symptoms and verify after patching
Check the logs for repeated worker crashes, problems reading sessions, or errors after starting services. These symptoms warrant further investigation, but symptoms alone cannot establish that an attack through these CVEs has occurred.
systemctl is-active php8.4-fpm nginx
sudo journalctl -b -u php8.4-fpm -u nginx -u apache2
uname -r
sudo journalctl -k -b
All 24 CVEs mentioned in this article are absent from the KEV edition dated 18 Nov. 2026, checked against the KEV JSON in CISA's official mirror with catalogVersion: 2026.11.18. This means there are no KEV date-added entries or remediation deadlines for these items in this edition. Absence from KEV does not mean there is no exploitation in the wild. The demonstrations in PHP's advisories are also not evidence of attacks against production systems.
I treat PHP installations that accept uploads and nginx installations with the modules covered by the advisories enabled as urgent patching work. For GCP FIPS, check that the modules are ready, then schedule a reboot in the earliest available maintenance window. Test login, uploads, and sessions before closing the work too.
Sources: Debian DSA-6641-1, PHP session mismatch, PHP session write, PHP ChangeLog, Debian DSA-6642-1, nginx advisories, Ubuntu nginx CVE, Ubuntu USN-9174-1, Ubuntu CVE-2026-93221. Information checked on 20 Nov. 2026. I'll come back and update this later.
Want us to set this up?
Get help with server setup, configuration, migration, or troubleshooting. Save time for the work that matters.
Hit something like this? Stuck somewhere?
Come trade notes on the LinuxThai board



Comments 0
No comments yet — be the first