Skip to content
PHP Patches Seven Critical RCE Vulnerabilities

PHP Patches Seven Critical RCE Vulnerabilities

Securityweek •Ionut Arghire • November 19, 2026

PHP on Thursday rolled out a fresh set of security patches as part of its four-week update schedule, including fixes for seven critical-severity remote code execution (RCE) vulnerabilities. First in line is CVE-2026-115560 , which was publicly disclosed last month, two days after PHP2Shell patches landed. Residing in the session upload progress feature, it could be triggered to write attacker data using one session serialization format and then read it using another. “A mismatched decoder can interpret part of a session key as serialized object data. An application with a suitable object gadget chain can then execute code with the privileges of the PHP worker,” PHP’s advisory reads. in line is CVE-2026-129481 , described as a use-after-free that occurs after a session shutdown has been interrupted, and which PHP describes as an incomplete fix for CVE-2026-109619, one of the two PHP2Shell flaws fixed in October and now widely exploited. “An attacker who can cause an application’s session cleanup to fail in this way may corrupt memory or crash a reused PHP worker. The use-after-free could potentially lead to remote code execution, but code execution through this specific field has not been demonstrated,” PHP notes, adding that PHP 8.2 is not affected. Another use-after-free, CVE-2026-129182 , covers additional exploitation scenarios for CVE-2026-109619, an RCE via stale global state. According to PHP, however, RCE via these scenarios has not been demonstrated. Impacting PHP 8.5 and later, CVE-2026-129474 is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE. “Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point,” PHP says. Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

First in line is CVE-2026-115560 , which was publicly disclosed last month, two days after PHP2Shell patches landed. Residing in the session upload progress feature, it could be triggered to write attacker data using one session serialization format and then read it using another. “A mismatched decoder can interpret part of a session key as serialized object data. An application with a suitable object gadget chain can then execute code with the privileges of the PHP worker,” PHP’s advisory reads. in line is CVE-2026-129481 , described as a use-after-free that occurs after a session shutdown has been interrupted, and which PHP describes as an incomplete fix for CVE-2026-109619, one of the two PHP2Shell flaws fixed in October and now widely exploited. “An attacker who can cause an application’s session cleanup to fail in this way may corrupt memory or crash a reused PHP worker. The use-after-free could potentially lead to remote code execution, but code execution through this specific field has not been demonstrated,” PHP notes, adding that PHP 8.2 is not affected. Another use-after-free, CVE-2026-129182 , covers additional exploitation scenarios for CVE-2026-109619, an RCE via stale global state. According to PHP, however, RCE via these scenarios has not been demonstrated. Impacting PHP 8.5 and later, CVE-2026-129474 is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE. “Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point,” PHP says. Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

“A mismatched decoder can interpret part of a session key as serialized object data. An application with a suitable object gadget chain can then execute code with the privileges of the PHP worker,” PHP’s advisory reads. in line is CVE-2026-129481 , described as a use-after-free that occurs after a session shutdown has been interrupted, and which PHP describes as an incomplete fix for CVE-2026-109619, one of the two PHP2Shell flaws fixed in October and now widely exploited. “An attacker who can cause an application’s session cleanup to fail in this way may corrupt memory or crash a reused PHP worker. The use-after-free could potentially lead to remote code execution, but code execution through this specific field has not been demonstrated,” PHP notes, adding that PHP 8.2 is not affected. Another use-after-free, CVE-2026-129182 , covers additional exploitation scenarios for CVE-2026-109619, an RCE via stale global state. According to PHP, however, RCE via these scenarios has not been demonstrated. Impacting PHP 8.5 and later, CVE-2026-129474 is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE. “Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point,” PHP says. Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

in line is CVE-2026-129481 , described as a use-after-free that occurs after a session shutdown has been interrupted, and which PHP describes as an incomplete fix for CVE-2026-109619, one of the two PHP2Shell flaws fixed in October and now widely exploited. “An attacker who can cause an application’s session cleanup to fail in this way may corrupt memory or crash a reused PHP worker. The use-after-free could potentially lead to remote code execution, but code execution through this specific field has not been demonstrated,” PHP notes, adding that PHP 8.2 is not affected. Another use-after-free, CVE-2026-129182 , covers additional exploitation scenarios for CVE-2026-109619, an RCE via stale global state. According to PHP, however, RCE via these scenarios has not been demonstrated. Impacting PHP 8.5 and later, CVE-2026-129474 is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE. “Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point,” PHP says. Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

“An attacker who can cause an application’s session cleanup to fail in this way may corrupt memory or crash a reused PHP worker. The use-after-free could potentially lead to remote code execution, but code execution through this specific field has not been demonstrated,” PHP notes, adding that PHP 8.2 is not affected. Another use-after-free, CVE-2026-129182 , covers additional exploitation scenarios for CVE-2026-109619, an RCE via stale global state. According to PHP, however, RCE via these scenarios has not been demonstrated. Impacting PHP 8.5 and later, CVE-2026-129474 is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE. “Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point,” PHP says. Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Another use-after-free, CVE-2026-129182 , covers additional exploitation scenarios for CVE-2026-109619, an RCE via stale global state. According to PHP, however, RCE via these scenarios has not been demonstrated. Impacting PHP 8.5 and later, CVE-2026-129474 is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE. “Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point,” PHP says. Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Impacting PHP 8.5 and later, CVE-2026-129474 is a use-after-free weakness that could allow an unauthenticated attacker to cause a fatal error and achieve RCE. “Exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point,” PHP says. Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Attackers able to influence session contents and interrupt the write of serialized data to a session file may trigger the deserialization of attacker-controlled content when the session is opened. Tracked as CVE-2026-126714 , the flaw could lead to RCE via a suitable object gadget chain in the application. PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

PHP also patched CVE-2026-129289 , a PHP-FPM request smuggling issue caused by PHP reading a request-body stream lazily, treating a request body as handled during request shutdown and skipping the normal cleanup that discards unread input. “PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

“PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. In PHP-FPM, an unauthenticated attacker can make those bytes form a separate FastCGI request, bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker,” PHP explains. The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

The seventh critical-severity vulnerability patched today, CVE-2026-129496 , resides in the timezone cache. PHP can retain a reference to it when writing a diagnostic to a PHP error log file during process startup, and a later diagnostic can access the freed cache before it is reset. “On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

“On affected configurations, a remote attacker can trigger memory corruption, cause a worker to crash, and potentially execute arbitrary code with the privileges of the PHP worker,” PHP explains. PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

PHP 8.6.0 and PHP 8.5.13 were rolled out with fixes for all critical bugs and for 10 high and medium-severity flaws. Patches for most issues were also included in PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. More information is available on PHP’s news archive page. Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Related: PHP Readies Critical Security Updates to Patch Another RCE Flaw Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Related: Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Related: Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Related: Splunk Patches Nearly 140 Flaws Across Three Core Products

Ionut Arghire is an international correspondent for SecurityWeek.

More from Ionut Arghire

PHP Readies Critical Security Updates to Patch Another RCE Flaw

Russian APT Poses as Employee of Hacked Firm to Breach Another US Organization

Chrome 158 Patches 204 Vulnerabilities

Critical Perforce Puppet RCE Exploited in Attacks

Oracle Patches 950 Vulnerabilities With November 2026 CSPU

AI Framework Autonomously Weaponized Flaws in Real Attacks, Google Says

MSP ScreenConnect Servers Targeted in Month-Long Campaign

Access Dental Management Data Breach Impacts Over 340,000

Nvidia Responds to Gentlemen Ransomware Claim

Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release

StepSecurity Secures $20 Million to Expand Supply Chain Protection

Critical Apache Roller, Axis Vulnerabilities Exploited in Attacks

The Governance Gap in Open-Weight AI and What to Do It

Splunk Patches Nearly 140 Flaws Across Three Core Products

F5 Patches Critical NGINX2Root Flaws as PoC Exploits Go Public

Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories

Flipboard Whatsapp Whatsapp Email