P3 · Modérée · Drupal
Drupal : vulnérabilité
Critical PHP update on Wednesday, October 21, 2026 (14:00 UTC) - PSA-2026-10-20
Cycle de mise à jour mensuel
Pourquoi ce niveau : Gravité pas encore publiée : à requalifier dès que l'éditeur ou la NVD la donne.
Ce qu'il faut faire
-
Vérifier si vous êtes concerné
Comparer la version installée aux versions corrigées ci-dessous.
drush status --field=drupal-version composer show drupal/core -
Corriger
Versions corrigées : voir l'avis de l'éditeur (lien dans les sources).
Mettre à jour le cœur ou le module concerné avec Composer, appliquer les mises à jour de base, vider les caches, sur chaque site.
composer update "drupal/core-*" --with-all-dependencies composer update drupal/<module> --with-all-dependencies drush updatedb -y && drush cache:rebuild -
En attendant le correctif
Désactiver le module concerné (
drush pm:uninstall <module>) si le correctif ne peut pas passer tout de suite, ou retirer la permission vulnérable aux rôles non administrateurs. -
Contrôler
drush status --field=drupal-versionetcomposer show drupal/<module>doivent afficher la version corrigée.Rapport de statut Drupal (
/admin/reports/status) sans alerte de sécurité.
Commandes indicatives (Debian ou Ubuntu) : à adapter à chaque serveur, après sauvegarde.
Description
PHP has announced a critical PHP security release for Wednesday, October 21, 2026, at 14:00 UTC. Reserve time to update PHP as soon as the release is available. If you manage PHP yourself, you’ll need to apply the update. If your host manages it, follow their communications for timing and any required action. Updating to a PHP release containing the patch to these vulnerabilities is the only complete mitigation. Site owners are responsible for maintaining the security of their hosting platform It is the policy of the Drupal Security Team that site owners are responsible for monitoring and maintaining the security of third-party libraries and any non-Drupal components of the application and hosting platform. In rare cases, the Drupal Security Team will post an informational public service announcement (PSA) such as this one, but the remit of the Drupal Security Team remains limited to code hosted on Drupal.org’s systems. Previous PSAs on third-party code in the Drupal ecosystem include: - External libraries and plugins - PSA-2011-002 - Various Third-Party Vulnerabilities - PSA-2019-09-04 - Third-Party Libraries and Supply Chains - PSA-2024-06-26 - Third-Party Libraries and Supply Chains - PSA-2025-09-17 This post is likely to be updated as the situation evolves and more information is available.