<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on jpcercal.com</title><link>https://jpcercal.com/en/tags/devops/</link><description>Recent content in Devops on jpcercal.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jpcercal.com/en/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>PHP2Shell: Two Critical PHP Vulnerabilities and What to Do Now</title><link>https://jpcercal.com/en/php2shell-two-critical-php-vulnerabilities/</link><pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate><guid>https://jpcercal.com/en/php2shell-two-critical-php-vulnerabilities/</guid><description>&lt;p&gt;Two critical flaws in the PHP runtime itself were disclosed on October 21, 2026: CVE-2026-109618 and CVE-2026-109619, nicknamed “PHP2Shell.” Both are CVSS 9.2 (v4.0) and can lead to unauthenticated remote code execution. Disclosure was moved up a day after the IDs leaked (&lt;a href="https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-php-security/"&gt;PHP Foundation&lt;/a&gt;). The bug is in PHP core, so your framework does not matter.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;The short version:&lt;/strong&gt; update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, restart every worker, and verify the running version. A WAF buys time; it is not a patch.&lt;/p&gt;</description></item></channel></rss>