Vulnerability Management, Patch/Configuration Management, Application security

PHP releases 18 security patches, including 7 critical flaws

Website development concept. PHP programming language inside magnifying glass in binary code.

The PHP Foundation on Nov. 19 released 18 patches for a new set of vulnerabilities, seven of which are critical.

Thursday’s patches come about one month after PHP2Shell — two critical flaws tracked as CVE-2026-109618 and CVE-2026-109619 — were disclosed and sent security team worldwide scrambling.  

Since the original PHP2Shell patches were released, the industry has seen a wave of outages caused by problems with routine maintenance, and earlier today JPMorganChase, one of the many banks that experienced an outage, reported that one of its third-parties was the target of a cyberattack that the bank claims was unrelated to the recent outage.

“Everyone is tired of hearing ‘patch now,’ but today really is a ‘patch-it-today’ kind of day,” said Keenan Skelly, founder and CEO at Divergent Labs, and a former senior policy advisor on cyber policy in the Biden administration.

Skelly noted that PHP runs everywhere, including a lot of places most people don’t think of as PHP: the vendor appliance in the company’s rack, the management console, or that plug-in nobody remembers installing. When last month’s PHP2Shell flaws came out, Skelly said attackers were using them within days, including against the management interfaces of security appliances.

Also on Thursday, PHP also flagged CVE-2026-115560, mainly because it sat for almost a month with nothing but a workaround, and one of the two things it needs to work — session upload progress — gets turned on by default.

“Most sites won’t be exploitable because the other condition is an unusual bit of code,” explained Skelly. “But be honest: can you tell me what every app and vendor product in your shop does with session handling? Most teams can’t, and that’s the real problem.”

Skelly advised updating to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 immediately. For teams that can’t, turn off session upload progress, restart PHP, and call all vendors to ask when their fixed build ships.

Ben Ronallo, director of cybersecurity operations at Black Duck, agreed that security teams should patch right away.

Ronallo said the fixed versions, 8.2.36, 8.3.37, 8.4.28 and 8.5.13, are out now, and last month’s PHP2Shell patches do not cover this one.

“If your PHP comes from a Linux distribution or a container image, check that your vendor has shipped the update,” said Ronallo. “Until then, turn off session upload progress in php.ini or the FPM pool configuration, not in application code.”

Steve Zurier
Steve Zurier has been a freelance writer and editor for SC Media since 2012. Now, Zurier writes daily news stories and edits SC Media’s Perspectives columns. A long-time member of the tech press, Zurier lives in Columbia, MD. During off-hours, Steve moonlights as an upright bassist for jazz and klezmer bands around the Baltimore/DC area.

Related Events

Get daily email updates

SC Media's daily must-read of the most current and pressing daily news

By clicking the Subscribe button below, you agree to SC Media Terms of Use and Privacy Policy.

You can skip this ad in 5 seconds