{"id":2440,"date":"2026-11-21T01:40:06","date_gmt":"2026-11-20T16:40:06","guid":{"rendered":"https:\/\/blog.coppe.jp\/?p=2440"},"modified":"2026-11-21T02:20:17","modified_gmt":"2026-11-20T17:20:17","slug":"drupal-sa-core-2026-017-critical-rce","status":"publish","type":"post","link":"https:\/\/blog.coppe.jp\/en\/2026\/11\/21\/drupal-sa-core-2026-017-critical-rce\/","title":{"rendered":"Drupal Critical Update (November 2026): Versions to Upgrade to and What to Do"},"content":{"rendered":"<p class=\"wp-block-paragraph\">On November 18, 2026, two security advisories for Drupal Core were released.<a href=\"https:\/\/www.drupal.org\/sa-core-2026-017\" target=\"_blank\" rel=\"noopener noreferrer\">SA-CORE-2026-017<\/a>(Critical \/ Remote code execution \/ CVE-2026-132165) and<a href=\"https:\/\/www.drupal.org\/sa-core-2026-018\" target=\"_blank\" rel=\"noopener noreferrer\">SA-CORE-2026-018<\/a>(Moderately critical \/ Gadget chain \/ CVE-2026-132166).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What was dangerous?<\/h2>\n\n\n<h3 class=\"wp-block-heading\">SA-CORE-2026-017: Critical\/RCE<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is the main one. The severity is Critical (18\/25). The vulnerability type is Remote code execution. The CVE is CVE-2026-132165.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Drupal core is for installation <code data-no-translation=\"\">install.php<\/code> It includes [a specific component\/package]. Under certain conditions, an attacker could attempt to reinstall the software via the installer. This could potentially lead to website hijacking or remote code execution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">According to the official documentation, the web server <code data-no-translation=\"\">settings.php<\/code> If the configuration prevents the modification of settings or changes to their permissions, some exploitation routes can be mitigated. In other words, it's not a case of \"just update and you're done\"; the permissions of the configuration files and the protection of the installer work together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The difficulty of exploitation is listed as \"Complex\" and \"A:None\" (no authentication). This doesn't mean anyone can easily exploit it. Nevertheless, it's classified as \"Critical,\" and since there is proof on the official side, it's not something that can be ignored.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SA-CORE-2026-018\uff1aModerately critical \/ Gadget chain<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The other vulnerability is Gadget chain (CVE-2026-132166). Its severity is Moderately critical (14\/25).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It cannot be directly exploited on its own. Another vulnerability allows untrusted data to be compromised. <code data-no-translation=\"\">unserialize()<\/code> The situation is such that if it extends to multiple points, it can be used as a stepping stone for RCE (Remote Compromise). The official statement also clearly says, \u201cThis issue is not directly exploitable.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Although it's easy to overlook because it was released at the same time as 017, read them separately in terms of priority. It's correct to understand that 017 is urgent, while 018 is something to be \"fixed along with the core update.\"<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who should be in a hurry?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The affected versions are the same for both advisories. For supported product lines, versions prior to the following are affected.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Drupal 10.6.x \u2192 <strong>10.6.22<\/strong> Updates are required for those below this level.<\/li>\n\n\n\n<li>Drupal 11.4.x \u2192 <strong>11.4.13<\/strong> Updates are required for those below this level.<\/li>\n\n\n\n<li>Drupal 11.3.x \u2192 <strong>11.3.22<\/strong> Updates are required for those below this level.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The end-of-life (EOL) situation is even more severe. Drupal 11.2.x and earlier, Drupal 10.5.x and earlier, and Drupal 8\/9 are outside of security coverage. For lineages that will not receive patches, it is necessary to simultaneously plan to upgrade to a supported major update and to protect the installer for the time being.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The following operational changes are particularly urgent.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The public site is running supported versions 10.6 \/ 11.3 \/ 11.4.<\/li>\n\n\n\n<li><code data-no-translation=\"\">core\/install.php<\/code> It remains in a state where it can be received from the outside.<\/li>\n\n\n\n<li><code data-no-translation=\"\">settings.php<\/code>(and environment variable files) remain writable from the web server<\/li>\n\n\n\n<li>The staging and development hosts are exposed to the internet via the same route as the production environment.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In my own operations, I also implemented a core update on the day of release. It wasn't a major change spanning multiple releases, but rather a migration to a security release within the same family. Major updates to contributing modules like Bootstrap and CAPTCHA can be discussed separately from this.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Actions to take<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Update the core to the security release.<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The first thing to do is to upgrade to the corrected version within the same major project. (If using Composer) <code data-no-translation=\"\">drupal\/core-recommended<\/code>(or <code data-no-translation=\"\">drupal\/core<\/code>) and its dependencies are updated, and the process goes through to DB update and cache rebuild.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Protect the installer<\/h3>\n\n\n<p class=\"wp-block-paragraph\">The official recommendation is to protect the installer in addition to upgrading. <code data-no-translation=\"\">install.php<\/code> It remains. It's only needed during a new installation; under normal operation, this entry point should be closed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The method is described in the official documentation. <a href=\"https:\/\/www.drupal.org\/docs\/administering-a-drupal-site\/security-in-drupal\/securing-the-installer-installphp\" target=\"_blank\" rel=\"noopener noreferrer\">Securing the installer (install.php)<\/a> It's all summarized. I'll just write the main points.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In the web server settings <code data-no-translation=\"\">\/core\/install.php<\/code> Reject (recommended)<\/li>\n\n\n\n<li>If you cannot access server settings on shared hosting, etc., the document root is... <code data-no-translation=\"\">.htaccess<\/code> \u3067 <code data-no-translation=\"\">install.php<\/code> .<\/li>\n\n\n\n<li>Deleting the files is an option, but be aware that they will revert to their original state every time you reinstall the core using Composer.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This protection is also effective as a temporary fix when a core update cannot be performed immediately. However, this is not a matter of stopping there. Both updates and protection must be carried out.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Review the permissions in settings.php \/ .env.<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Even in the explanation for 017, the web server <code data-no-translation=\"\">settings.php<\/code> Configurations that prevent writing or changing permissions can limit some abusive routes. It's worth checking whether the system remains writable immediately after installation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In Bedrock or Composer-based configurations, DB connection information and keys are <code data-no-translation=\"\">.env<\/code> They are often located nearby. The inventory should also include checking whether they are not placed in a location accessible from the web, or whether they are in a state where web server users can unnecessarily write to them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This doesn't mean that \"if you severely restrict permissions, updates won't be necessary.\" Rather, it's a confirmation process to reduce the number of remaining entry points, assuming updates will be necessary.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The heaviest update this time is SA-CORE-2026-017. It is a Critical RCE, albeit conditionally, so if you are running a public Drupal, first check the version and upgrade to the corrected version.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>10.6.x means 10.6.22 or later.<\/li>\n\n\n\n<li>11.4.x is 11.4.13 or later.<\/li>\n\n\n\n<li>11.3.x means 11.3.22 or later.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In addition <code data-no-translation=\"\">install.php<\/code> Close it,<code data-no-translation=\"\">settings.php<\/code> Review the permissions of the environment variable file. The 018 Gadget chain cannot be directly exploited on its own, but since it is included in the same security release, it can be shut down as a whole.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The following two sources are the official primary sources.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.drupal.org\/sa-core-2026-017\" target=\"_blank\" rel=\"noopener noreferrer\">SA-CORE-2026-017<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.drupal.org\/sa-core-2026-018\" target=\"_blank\" rel=\"noopener noreferrer\">SA-CORE-2026-018<\/a><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Please start checking and updating your version today.<\/p>","protected":false},"excerpt":{"rendered":"<p>Drupal SA-CORE-2026-017 (Critical) and 018, released on November 18, 2026. This document summarizes the dangers, the versions that require immediate upgrades, and the necessary actions.<\/p>","protected":false},"author":2,"featured_media":2446,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2440","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts\/2440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/comments?post=2440"}],"version-history":[{"count":3,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts\/2440\/revisions"}],"predecessor-version":[{"id":2445,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts\/2440\/revisions\/2445"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/media\/2446"}],"wp:attachment":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/media?parent=2440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/categories?post=2440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/tags?post=2440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}