Vulnerability in drupal (CVE-2026-6366)
Summary
Vulnerability in drupal (CVE-2026-6366). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 10.5.9, 10.6.7, 11.2.11, 11.3.7 or later.
Original description
The description as published by the source.
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Drupal Drupal core allows Object Injection.
This issue affects Drupal core: from 8.0.0 before 10.5.9, from 10.6.0 before 10.6.7, from 11.0.0 before 11.2.11, from 11.3.0 before 11.3.7.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-6366 has been found in drupal.
Successful exploitation can lead to full system takeover. CVSS score: 6.6/10.
What to do: upgrade drupal to 10.5.9, 10.6.7, 11.2.11, 11.3.7 or later.
If unsure, ask your IT team or search "drupal CVE-2026-6366" on the vendor's site.
CVE-2026-6366 (drupal) — CWE-915 / CVSS v3 6.6
Attack vector: remote (network-reachable) / no user interaction
Patched: 10.5.9, 10.6.7, 11.2.11, 11.3.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-915) exists in drupal.
Check the vendor advisory for the affected versions of drupal.
Severity: Medium (CVSS 6.6/10). Successful exploitation can lead to full system takeover.
Update to 10.5.9, 10.6.7, 11.2.11, 11.3.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'drupal' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'drupal' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
drupalを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade drupal to 10.5.9, 10.6.7, 11.2.11, 11.3.7ステージング環境で 10.5.9, 10.6.7, 11.2.11, 11.3.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch mlhess@drupal.org
- web github.com