Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY21 SECURITY RECORDS

Drupal

core

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Drupal. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-9082 20 May 2026 Drupal core: 8.9.0 < 10.4.10, 10.5.0 < 10.5.10, 10.6.0 < 10.6.9, 11.0.0 < 11.1.10, 11.2.0 < 11.2.12, 11.3.0 < 11.3.10 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-5256 28 Sep 2023 10.1 ≤ 10.1.4; 10.0 ≤ 10.0.11; 9.5 ≤ 9.5.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-31250 26 Apr 2023 7.0 < 7.96; 10.0 < 10.0.8; 9.5 < 9.5.8; 9.4 < 9.4.14 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-25278 26 Apr 2023 9.4 < 9.4.3; 9.3 < 9.3.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-25277 26 Apr 2023 9.4 < 9.4.3; 9.3 < 9.3.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-25276 26 Apr 2023 9.4 < 9.4.3; 9.3 < 9.3.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-25275 26 Apr 2023 9.4 < 9.4.3; 9.3 < 9.3.19; 7 < 7.91 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-25274 26 Apr 2023 9.3 < 9.3.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-25273 26 Apr 2023 9.3 < 9.3.12; 9.2 < 9.2.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-25270 16 Feb 2022 9.3.x < 9.3.6; 9.2.x < 9.2.13 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-25271 16 Feb 2022 9.3.x < 9.3.6; 9.2.x < 9.2.13; 7.x < 7.88 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13677 11 Feb 2022 9.2.x < 9.2.6; 9.1.x < 9.1.13; 8.9.x < 8.9.19 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13676 11 Feb 2022 9.2 < 9.2.6; 9.1 < 9.1.13; 8.9 < 8.9.19 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13670 11 Feb 2022 8.8.x < 8.8.10; 8.9.x < 8.9.6; 9.0.x < 9.0.6 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13674 11 Feb 2022 9.2 < 9.2.6; 9.1 < 9.1.13; 8.9 < 8.9.19 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13675 11 Feb 2022 9.2.x < 9.2.6; 9.1.x < 9.1.13; 8.9.x < 8.9.19 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13672 11 Feb 2022 9.1.x < 9.1.7; 9.0.x < 9.0.12; 8.9.x < 8.9.14; 7.x < 7.80 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13669 11 Feb 2022 8.8.x < 8.8.10; 8.9.x < 8.9.6; 9.0.x < 9.0.6 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-13668 11 Feb 2022 8.8.x < 8.8.10; 8.9.x < 8.9.6; 9.0.x < 9.0.6 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2019-6340 21 Feb 2019 Drupal Core: 8.5 < 8.5.11, 8.6 < 8.6.10 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-7602 19 Jul 2018 core: unspecified < 7.59, unspecified < 8.5.3, unspecified < 8.4.8 Solution:; Upgrade to the most recent version of Drupal 7 or 8 core.; If you are running 7.x, upgrade to Drupal 7.59.; If you are running 8.5.x, upgrade to Drupal 8.5.3.; If you are running 8.4.x, upgrade to Drupal 8.4.8. (Drupal 8.4.x is no longer supported and we don't normally provide security releases for unsupported minor releases. However, we are providing this 8.4.x release so that sites can update as quickly as possible. You should update to 8.4.8 immediately, then update to 8.5.3 or the latest secure release as soon as possible.); If you are unable to update immediately, or if you are running a Drupal distribution that does not yet include this security release, you can attempt to apply the patch below to fix the vulnerability until you are able to update completely:; Patch for Drupal 8.x (8.5.x and below); Patch for Drupal 7.x; These patches will only work if your site already has the fix from SA-CORE-2018-002 applied. (If your site does not have that fix, it may already be compromised.) Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.