<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Memory-Safety on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/memory-safety/</link>
    <description>Recent content in Memory-Safety on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Fri, 23 Oct 2026 16:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/memory-safety/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PHP: Twenty-Nine Years Of Leaving The Door Open</title>
      <link>https://blogs.damiendye.uk/en/security/php-twenty-nine-years-of-leaving-the-door-open/</link>
      <pubDate>Fri, 23 Oct 2026 16:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/security/php-twenty-nine-years-of-leaving-the-door-open/</guid>
      <description>PHP2Shell, disclosed 21st October 2026, is a memory-safety RCE in every PHP back to 5.4. 757 interpreter CVEs from NVD, the C engine, type juggling, WordPress, web shells, the php.net breaches, half of PHP sites on unsupported versions, the one-process deployment that turns every bug into the lot, and why to leave it for Go or Rust.</description>
    </item>
  </channel>
</rss>
