<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PHP Group on PhllapsNET</title>
    <link>https://www.phllaps.net/tags/php-group/</link>
    <description>Recent content in PHP Group on PhllapsNET</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.phllaps.net/tags/php-group/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PHP Memory Corruption Vulnerability</title>
      <link>https://www.phllaps.net/posts/php-memory-corruption-vulnerability/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.phllaps.net/posts/php-memory-corruption-vulnerability/</guid>
      <description>&lt;div style=&#34;background:#6b7280;color:white;padding:16px 18px;border-radius:14px;font-weight:800;font-size:18px;display:flex;align-items:center;gap:12px;box-shadow:0 10px 24px rgba(0,0,0,0.18);&#34;&gt;&lt;span style=&#34;font-size:24px;&#34;&gt;🚨&lt;/span&gt;&lt;span&gt;SEVERITY: UNKNOWN&lt;/span&gt;&lt;span style=&#34;opacity:0.95;font-weight:700;margin-left:auto;&#34;&gt;Security Advisory&lt;/span&gt;&lt;/div&gt;&#xA;&lt;h2 id=&#34;tldr-&#34;&gt;TL;DR 📌&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;PHP contains an out-of-memory corruption vulnerability that allows for unauthenticated remote code execution.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Listed in CISA KEV&lt;/strong&gt; (2026-10-26) — this is being exploited in the wild.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Check the advisory for fixed releases&lt;/strong&gt; — remediation detail is in the vendor link below.&lt;/li&gt;&#xA;&lt;li&gt;CVEs: CVE-2026-109618.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;what-it-is&#34;&gt;What it is&lt;/h2&gt;&#xA;&lt;p&gt;CVE-2026-109618 is a memory corruption flaw in PHP that allows unauthenticated remote code execution. The PHP Group has not published detail beyond this summary, so the specific component, module, or code path involved is not yet clear.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PHP Stale Internal Request-State Vulnerability</title>
      <link>https://www.phllaps.net/posts/php-stale-internal-request-state-vulnerability/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.phllaps.net/posts/php-stale-internal-request-state-vulnerability/</guid>
      <description>&lt;div style=&#34;background:#dc2626;color:white;padding:16px 18px;border-radius:14px;font-weight:800;font-size:18px;display:flex;align-items:center;gap:12px;box-shadow:0 10px 24px rgba(0,0,0,0.18);&#34;&gt;&lt;span style=&#34;font-size:24px;&#34;&gt;🚨&lt;/span&gt;&lt;span&gt;SEVERITY: HIGH — CVSS 8.1&lt;/span&gt;&lt;span style=&#34;opacity:0.95;font-weight:700;margin-left:auto;&#34;&gt;Security Advisory&lt;/span&gt;&lt;/div&gt;&#xA;&lt;h2 id=&#34;tldr-&#34;&gt;TL;DR 📌&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;PHP contains a stale internal request-state vulnerability that allows for unauthenticated remote code execution.&lt;/li&gt;&#xA;&lt;li&gt;Highest CVSS: &lt;strong&gt;8.1 (High)&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Listed in CISA KEV&lt;/strong&gt; (2026-10-26) — this is being exploited in the wild.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Fixed in &lt;code&gt;10.2.7&lt;/code&gt;, &lt;code&gt;11.1.4&lt;/code&gt;, &lt;code&gt;11.2.4&lt;/code&gt;, &lt;code&gt;12.1.4&lt;/code&gt;&lt;/strong&gt; — upgrade to this release or later.&lt;/li&gt;&#xA;&lt;li&gt;CVEs: CVE-2026-109619.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;what-it-is&#34;&gt;What it is&lt;/h2&gt;&#xA;&lt;p&gt;This is a memory-safety flaw in PHP&amp;rsquo;s internal request handling. PHP maintains global state that temporarily points into memory allocated for the current request. In certain scenarios that state is not correctly reset between requests, or gets repopulated after a reset, so it ends up referencing request memory that has already been freed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
