<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[EveryHost Magento Notes]]></title><description><![CDATA[Practical notes on running, patching and troubleshooting Magento and Mage-OS stores, written by Simon Bumford at EveryHost, a UK Magento hosting company.]]></description><link>https://everyhost.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6af091faf8026889db2bf4d7/73677f63-d026-43ba-83f8-5ca663d9203b.png</url><title>EveryHost Magento Notes</title><link>https://everyhost.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 18:33:12 GMT</lastBuildDate><atom:link href="https://everyhost.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Magento security patch won't apply? The usual causes and how to fix them]]></title><description><![CDATA[Magento security patch failing, or not showing as applied? The common causes, from old -p releases to skipped months, and how to check each.]]></description><link>https://everyhost.hashnode.dev/magento-security-patch-won-t-apply-the-usual-causes-and-how-to-fix-them</link><guid isPermaLink="true">https://everyhost.hashnode.dev/magento-security-patch-won-t-apply-the-usual-causes-and-how-to-fix-them</guid><category><![CDATA[Magento]]></category><category><![CDATA[magento 2]]></category><category><![CDATA[Security]]></category><category><![CDATA[PHP]]></category><dc:creator><![CDATA[Simon Bumford]]></dc:creator><pubDate>Sun, 08 Nov 2026 15:25:47 GMT</pubDate><content:encoded><![CDATA[<p>Since July 2026, Adobe has shipped Magento security fixes as monthly isolated patches instead of new -pN releases. Each month's patch goes on top of the latest -p release for your version, and on top of every earlier monthly patch. It's a sensible system, but it trips people up. Most "this patch won't apply" and "we patched but the scanner still says vulnerable" problems come back to the same handful of causes.</p>
<p>Here they are, roughly in the order I'd check them.</p>
<h2>First, find out exactly what you're running</h2>
<p>Everything below depends on your exact version, so start there:</p>
<pre><code class="language-bash">php bin/magento --version
</code></pre>
<p>Then compare it with the latest patch level for your release line. Adobe's knowledge base article for the October 2026 patches, <a href="https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-49323">ka-49323</a>, lists the -p release each line has to be on first:</p>
<table>
<thead>
<tr>
<th>Release line</th>
<th>Must be on</th>
</tr>
</thead>
<tbody><tr>
<td>2.4.9</td>
<td>2.4.9</td>
</tr>
<tr>
<td>2.4.8</td>
<td>2.4.8-p5</td>
</tr>
<tr>
<td>2.4.7</td>
<td>2.4.7-p10</td>
</tr>
<tr>
<td>2.4.6</td>
<td>2.4.6-p15</td>
</tr>
<tr>
<td>2.4.5</td>
<td>2.4.5-p17</td>
</tr>
<tr>
<td>2.4.4</td>
<td>2.4.4-p18</td>
</tr>
</tbody></table>
<p>I keep a <a href="https://everyhost.co.uk/magento-end-of-life">Magento and Mage-OS version and patch tracker</a> that shows the latest patch for each version and how long each one is supported, which saves digging through Adobe's release notes.</p>
<h2>Cause 1: you're not on the latest -p release</h2>
<p>The monthly patches are built against one specific base: the last -p release for your line. If you're on 2.4.7-p6, the 2.4.7 patch was built for 2.4.7-p10, so it won't apply cleanly.</p>
<p><strong>Fix:</strong> upgrade to the latest -p release for your line first, on a staging copy, then apply the monthly patches. That's a proper version upgrade, so test it like one: checkout, payment, search, and anything that talks to your ERP or POS.</p>
<h2>Cause 2: you skipped a month</h2>
<p>Adobe expects the monthly patches to go on in order. The October patch assumes July, August and September are already there. If one is missing, the later ones can fail on files the missing patch should have changed.</p>
<p><strong>Fix:</strong> apply them in release order, July first. If you're not sure which are already in, ask whoever deploys your store to show you the patch list in your repository, or use the checks further down.</p>
<h2>Cause 3: you're on Magento Open Source 2.4.6 or older</h2>
<p>This isn't a technical failure, it's a download problem. Adobe's knowledge base says Open Source merchants "can only download patches for version 2.4.7 or later". The October patches for 2.4.4-p18, 2.4.5-p17 and 2.4.6-p15 need an Adobe Commerce licence.</p>
<p><strong>Fix:</strong> you have three options:</p>
<ul>
<li>Upgrade to 2.4.7-p10 or later. This is the one I'd recommend.</li>
<li>Use third-party backports. <a href="https://sansec.io/research/blockstrap-magento-rce">Sansec mentions</a> Happy Horizon's backported patches for these versions, with no warranty from Sansec.</li>
<li>Move to Mage-OS, the community fork of Magento Open Source. Mage-OS 3.6.0, released on 14 October, includes Adobe's October BlockStrap fix.</li>
</ul>
<h2>Cause 4: the deploy "worked" but the fix isn't in the code</h2>
<p>This is the one that catches experienced teams. Sansec points out two ways it happens:</p>
<ul>
<li>Composer patch plugins can skip a hunk without failing the build.</li>
<li>Deploy scripts that run <code>patch ... || true</code> ignore failed hunks completely.</li>
</ul>
<p>There's a third: Adobe published the October fixes as isolated patch files only, with no Composer packages. A fresh <code>composer install</code> gives you the unpatched base code, so if your build doesn't apply the patch files, the fix silently disappears on the next deploy.</p>
<p><strong>Fix:</strong> check the code on the server itself, not the deploy log. Adobe's Commerce Version Tool reports each CVE as PROTECTED, VULNERABLE or UNKNOWN:</p>
<pre><code class="language-bash">php vendor/bin/patch-status
</code></pre>
<p>For the October BlockStrap fix specifically, Sansec gives this check:</p>
<pre><code class="language-bash">grep -c resolveDeferredDirectives vendor/magento/framework/Filter/Template.php
</code></pre>
<p>A result of 0 means the fix is missing. On Mage-OS, the file is <code>vendor/mage-os/framework/Filter/Template.php</code>.</p>
<h2>Cause 5: <code>patch-status</code> isn't there</h2>
<p>The Commerce Version Tool ships inside the July 2026 isolated patch. If <code>vendor/bin/patch-status</code> doesn't exist, that's a sign the July patch never went on, so check the later months too (see cause 2).</p>
<p><strong>Fix:</strong> apply the July patch first, then the rest in order.</p>
<h2>Cause 6: the September StyleSmuggler hotfix is missing</h2>
<p>The October patch does <strong>not</strong> include the September hotfix for StyleSmuggler (VULN-39341). Adobe says it has to be applied separately, and Sansec says to install it before the October patch. You need both.</p>
<p>Check it with:</p>
<pre><code class="language-bash">vendor/bin/magento-patches -n status | grep "39341\|Status"
</code></pre>
<p>One thing that looks like a failure but isn't: with the hotfix in place, the October patch reports line offsets for <code>Preview.php</code> and <code>AbstractTemplate.php</code>. According to Sansec, the hunks still apply. Offsets are fine. "Hunk FAILED" is not.</p>
<h2>Cause 7: you're on 2.4.8-p5 and patched on 13 October</h2>
<p>The first 2.4.8-p5 October patch left out a change to <code>EmailAddress.php</code> for CVE-2026-91013, another bug in the same bulletin. Adobe replaced the file on 14 October and published the missing change separately as <code>248p5-2026-10-002-CE</code>. Both versions contain the BlockStrap fix.</p>
<p>Check it with:</p>
<pre><code class="language-bash">grep -c QUOTED_LOCAL_PART_PATTERN vendor/magento/framework/Validator/EmailAddress.php
</code></pre>
<p>If that prints 0, apply <code>248p5-2026-10-002-CE</code>.</p>
<h2>Not a problem: the strange file in your Magento root</h2>
<p>After the October patch, some people find an empty file in the Magento root with a 64-character name starting <code>976bc24c</code>. Sansec explains it's a lock file the patch creates by mistake: to fix a path traversal bug, lock files are now named after a SHA-256 hash, and this one ends up in the root. Every patched store gets the same name. You can delete it or add it to <code>.gitignore</code>. It's tracked as <a href="https://github.com/magento/magento2/issues/41535">magento/magento2#41535</a>.</p>
<h2>After the patch applies</h2>
<p>If your store runs in production mode, recompile and flush the cache after the patch, on staging first:</p>
<pre><code class="language-bash">php bin/magento setup:di:compile
php bin/magento cache:flush
</code></pre>
<p>Then run <code>patch-status</code> and the grep checks again, and keep the output. If someone else looks after your store, ask them for that output after every monthly patch. It takes a minute and tells you more than any "all done" email.</p>
<h2>Quick checklist</h2>
<ol>
<li>Check your version with <code>bin/magento --version</code>.</li>
<li>Get onto the latest -p release for your line.</li>
<li>Apply the monthly patches in order, from July.</li>
<li>Keep the September StyleSmuggler hotfix in place.</li>
<li>On 2.4.8-p5, check for the <code>002</code> email patch.</li>
<li>Recompile and flush the cache if you're in production mode.</li>
<li>Check in code: <code>patch-status</code>, then the grep checks.</li>
<li>Keep a record, and do it again next month.</li>
</ol>
<p>If your version isn't getting patches any more, that's the real problem to solve. The <a href="https://everyhost.co.uk/magento-end-of-life">version and patch tracker</a> shows where each release stands.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-49323">Adobe KB ka-49323: Security update available for Adobe Commerce, APSB26-153</a></li>
<li><a href="https://www.adobe.com/trust/security/products/commerce/apsb26-153.html">Adobe security bulletin APSB26-153</a></li>
<li><a href="https://sansec.io/research/blockstrap-magento-rce">Sansec: BlockStrap, Magento and Adobe Commerce RCE (CVE-2026-103849)</a></li>
<li><a href="https://experienceleague.adobe.com/en/docs/commerce-knowledge-base/kb/announcements/commerce-apsb26-146">Adobe hotfix notice for APSB26-146 (VULN-39341)</a></li>
</ul>
]]></content:encoded></item></channel></rss>