Yesterday afternoon, the Drupal Security Team published two simultaneous advisories against Drupal core: SA-CORE-2026-017, rated Critical and describing a remote code execution vulnerability, and SA-CORE-2026-018, rated Moderately Critical and describing a gadget chain flaw. When the Drupal Security Team labels something Critical RCE in core, that is the highest-urgency classification the project issues, and it demands same-day attention on every site you manage.
What shipped
The two advisories dropped within minutes of each other on Wednesday, November 18, 2026.
SA-CORE-2026-017 (Critical, Remote Code Execution): This is the more severe of the two. A remote code execution class of vulnerability in Drupal core means an attacker can, under the right conditions, run arbitrary code on the server without needing prior access. The specific attack vector, affected subsystem, and exact versions covered are detailed in the advisory itself. We are not speculating on those details here because the advisory page is authoritative and version ranges can be nuanced. Head directly to the SA-CORE-2026-017 advisory to confirm which versions are affected and what the patched releases are.
SA-CORE-2026-018 (Moderately Critical, Gadget Chain): A gadget chain vulnerability is typically a deserialization or object injection issue where an attacker assembles a sequence of existing code pieces in the application to reach a dangerous outcome, often escalating to code execution or privilege escalation. Moderately Critical is one tier below Critical in Drupal's risk scale, but a gadget chain in core is not something to defer. Check the SA-CORE-2026-018 advisory for affected versions and the patch.
Both advisories affect Drupal core. No contributed module or theme is at fault here. That means every Drupal site on a vulnerable version is exposed, regardless of which contrib modules it runs.
Our take
Two core advisories in the same release window is unusual and tells us the Security Team likely coordinated these fixes together to minimize patch fatigue. That is good process from the team. For agencies, it means one upgrade event covers both issues, which is better than two separate emergency windows.
On the RCE specifically: in fifteen-plus years of running Drupal sites for clients, we treat any Critical RCE in core as a fire drill, not a planned sprint item. The risk model is straightforward. If the vulnerability is publicly disclosed and a proof-of-concept surfaces, automated scanners will find unpatched sites within hours. Waiting until your next maintenance window is not an acceptable posture here.
On the gadget chain: we know agencies that would look at "Moderately Critical" and schedule it for the weekend. We would not, and here is why. Gadget chains are frequently the prerequisite step for a more damaging exploit chain. An attacker who can influence deserialization may be able to pivot to full code execution even if the advisory does not describe it that way directly. Treat it as Critical-adjacent until you know more.
What about sites on managed hosting? Kinsta, WP Engine (for WordPress clients), Acquia, and Pantheon all typically push core security patches on an accelerated schedule for managed Drupal plans. If your Drupal client sites are on Acquia or Pantheon managed plans, check your hosting dashboard before you do anything else. You may already be patched. If you manage your own servers or use unmanaged VPS hosting, the patch responsibility is entirely yours.
The honest trade-off on speed vs. process: our standard Drupal upgrade process involves staging, a smoke test, and a quick Lighthouse and accessibility pass before we touch production. For a Critical RCE, we compress that timeline. We still do staging (it takes 20 minutes, not a day), we still run a smoke test (login, content edit, cron, search), but we skip the performance benchmarking. The risk of a broken cache header is vastly lower than the risk of a compromised server.
On SA-CORE-2026-018 and older Drupal 10 sites: gadget chain vulnerabilities sometimes have a wider version range than you expect. If you are running any Drupal 10 sites that have not been kept current on minor releases, check whether the advisory covers your exact minor version. Drupal's 8-month minor security support window (a policy change we covered earlier this year) means some older minor versions may no longer receive patches at all.
What to do right now
- Pull up the two advisories (links below) and confirm which Drupal core versions are vulnerable and which are patched.
- Check your managed hosting dashboards first. Acquia and Pantheon often auto-apply core security releases. Confirm before duplicating effort.
- Clone production to staging, apply the update, run a smoke test. For a standard Drupal site with no custom modules touching core internals, this is a 30-45 minute operation.
- Promote to production the same day. Do not wait for end-of-week maintenance if you are on a vulnerable version.
- For sites on older Drupal 10 minor releases, check whether the advisory covers your version. If your minor is past its 8-month support window, the upgrade path is to the current minor first, then patch.
- Document the patch event in your client communication log. If a client asks later whether their site was patched, you want a timestamped record.
Originally referenced: SA-CORE-2026-017 and SA-CORE-2026-018 on Drupal.org Security Advisories.
If you are managing Drupal sites and need help triaging or applying these patches quickly, especially across a fleet of client sites, get in touch. We can turn around a patched and tested deployment the same day.



