CVE-2025-4416: Drupal Events Log Track · Unthrottled Resource Allocation
Affects Drupal Events Log TrackSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.0.2 or 3.1.11 soon.
Data as of 2 Nov 2026, 19:15 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 4.0.2, 3.1.11
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade Drupal Events Log Track to 4.0.2 or 3.1.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Drupal Events Log Track | Affected
| Fixed in
|
AI-suggested
No explicit patch or remediation links are provided in the data. Since fixed versions are indicated as 3.1.11 and 4.0.2, upgrading to at least these versions is recommended to mitigate the vulnerability. There is no indication that this is a cloud service; therefore, manual patching or upgrading is required.
Description
CVE-2025-4416 is a high-severity vulnerability in the Drupal Events Log Track module. It involves allocation of resources without limits or throttling, which can lead to excessive resource consumption. This affects versions from 0.0.0 before 3.1.11 and from 4.0.0 before 4.0.2. The vulnerability impacts availability but does not affect confidentiality or integrity.