English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

Drupal core fixes two remote code execution flaws in versions 10 and 11

On 18 November 2026, Drupal released security advisories SA-CORE-2026-017 and SA-CORE-2026-018, fixing vulnerabilities that allow remote arbitrary code execution. Unpatched Drupal 10 and 11 sites are affected, as are installations still running end-of-life branches.

What to do now Illustration photo (cyber security)
CVSS severity—
EPSS probability—
ExploitationNot observed
PatchAvailable
Product
Drupal
Affected versions
Drupal 11.4.x before 11.4.13, 11.x before 11.3.22, versions before 10.6.22; 11.2.x, 9.x and 8.x branches are end-of-life
Fixed in
11.4.13, 11.3.22, 10.6.22
CVE
CVE-2026-132165

France's CERT-FR issued advisory CERTFR-2026-AVI-1579 on 19 November 2026. It covers several vulnerabilities in Drupal core that the project disclosed a day earlier in advisories SA-CORE-2026-017 and SA-CORE-2026-018. The flaws are tracked as CVE-2026-132165 and CVE-2026-132166.

According to the advisory, a remote attacker can use these flaws to run arbitrary code on the server hosting the site. For an internet-facing CMS, this can lead to full takeover of the site and its data. The advisory does not name the affected components or the conditions for exploitation, such as whether authentication is needed.

Three branches are affected: Drupal 11.4.x before 11.4.13, other 11.x releases before 11.3.22, and versions before 10.6.22. The fixed releases are 11.4.13, 11.3.22 and 10.6.22.

Drupal points out that the 11.2.x, 9.x and 8.x branches are end-of-life and will not get security fixes. Sites still on those versions need to move to a supported branch to be protected.

The source does not say whether the vulnerabilities are being exploited. It also describes no workaround: the only remedy given is to apply the vendor's patches.

Action plan

What to do now

  1. Update Drupal to 11.4.13, 11.3.22 or 10.6.22, depending on the branch you run.
  2. Identify any sites still on Drupal 11.2.x, 9.x or 8.x and schedule their migration to a supported branch now, as these versions will not be patched.
  3. Read Drupal advisories SA-CORE-2026-017 and SA-CORE-2026-018 on drupal.org for details of the fixes.
  4. As general good practice, review web server logs and file integrity on exposed sites for signs of suspicious activity.

Sources