Vendor scorecard
CISA lists 5 Drupal vulnerabilities as exploited in the wild, 1 of them added in the last 12 months (up from 0 in the 12 months before). 2 (40%) are known to be used in ransomware campaigns. For entries added in the last two years, the median time from CVE publication to the KEV listing was 2 days. Most affected: Core (3), Drupal core (1), Drupal Core (1).
| Product | KEV entries |
|---|---|
| Core | 3 |
| Drupal core | 1 |
| Drupal Core | 1 |
| CVE | Vulnerability | Added |
|---|---|---|
| CVE-2026-9082 | Drupal Core SQL Injection VulnerabilityCore | |
| CVE-2018-7602 | Drupal Core Remote Code Execution VulnerabilityRANSOMWARECore | |
| CVE-2019-6340 | Drupal Core Remote Code Execution VulnerabilityCore | |
| CVE-2020-13671 | Drupal core Un-restricted Upload of FileDrupal core | |
| CVE-2018-7600 | Drupal Core Remote Code Execution VulnerabilityRANSOMWAREDrupal Core |
Get an email when CISA adds the next Drupal CVE.
How to read this: CISA KEV lists vulnerabilities with reliable evidence of exploitation; a vendor with many entries is often one with a large, internet-facing install base, not necessarily worse engineering. "Publication → KEV" is the median number of days between the CVE's publication and its addition to KEV, for entries added in the last 24 months (1 entries); it is an upper bound on how long defenders had, since exploitation usually starts before the listing. Under NIS2 article 21(2)(d), supplier security is part of your risk management; this page is a starting point for that review. Compare vendors on the scorecard index.
We assess supplier security for NIS2 and DORA, from exploited-CVE history and patch response to contract clauses and evidence packs.
Get in touch →