<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remote Code Execution on CybersecurityOS</title><link>http://www.cybersecurityos.net/tags/remote-code-execution/</link><description>Recent content in Remote Code Execution on CybersecurityOS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 11:06:44 +0000</lastBuildDate><atom:link href="http://www.cybersecurityos.net/tags/remote-code-execution/index.xml" rel="self" type="application/rss+xml"/><item><title>PHP2Shell: What We Know About CVE-2026-109618 and CVE-2026-109619, and What to Do Today</title><link>http://www.cybersecurityos.net/posts/vuln/php2shell-cve-2026-109618-109619/</link><pubDate>Wed, 21 Oct 2026 10:45:37 +0000</pubDate><guid>http://www.cybersecurityos.net/posts/vuln/php2shell-cve-2026-109618-109619/</guid><description>&lt;p&gt;On October 20, two critical vulnerabilities in PHP core leaked a day before their planned disclosure. They&amp;rsquo;re tracked as &lt;strong&gt;CVE-2026-109618&lt;/strong&gt; and &lt;strong&gt;CVE-2026-109619&lt;/strong&gt;, and the exploit tool that leaked with them has a name built for headlines: &lt;strong&gt;PHP2Shell&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This one is different from the usual CMS plugin bug. The flaws sit in the interpreter, not in WordPress, Laravel, or your own code. If a server runs PHP, it&amp;rsquo;s in scope until proven otherwise.&lt;/p&gt;</description></item></channel></rss>