CVE-2025-4416: Allocation of Resources Without Limits or Throttling vulnerability in Drupal Events Log Track allows Excessive

This month

HIGH 7.5REMOTEUPGRADE

CVE-2025-4416 is a high-severity flaw (CVSS 7.5) affecting events log track. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Allocation of Resources Without Limits or Throttling vulnerability in Drupal Events Log Track allows Excessive Allocation.This issue affects Events Log Track: from 0.0.0 before 3.1.11, from 4.0.0 before 4.0.2.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-770
Published	2025-05-21
Last modified	2026-06-17

Publisher (CNA): Drupal.org · Vendor: events log track project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-21 17:15 UTCPublished CVE record published
2026-06-17 09:33 UTCUpdated Record last modified

events log track project events log track UPGRADE

Affected: < 3.1.11 · >= 4.0.0 and < 4.0.2

Fixed in: 3.1.11, 4.0.2

Safe to downgrade to: a release before 4.0.0

1. Check installed version

apt-cache policy events-log-track || rpm -q events-log-track || events-log-track --version

2. UPGRADE to 3.1.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade events-log-track

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade events-log-track

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)

apt-cache madison events-log-track sudo apt install events-log-track=<VERSION_BEFORE_4.0.0> sudo apt-mark hold events-log-track

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list events-log-track sudo dnf downgrade events-log-track-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add events-log-track

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-4416?

events log track: upgrade to 3.1.11, 4.0.2. Exact commands for each OS are on this page.

Is CVE-2025-4416 being exploited?

CVE-2025-4416 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-4416 affect?

CVE-2025-4416 affects events log track. Severity is high (CVSS 7.5). Allocation of Resources Without Limits or Throttling vulnerability in Drupal Events Log Track allows Excessive Allocation.This issue affects Events Log Track: from 0.0.0 before 3.1.11, from 4.0.0 before 4.0.2.

How urgent is CVE-2025-4416?

Priority 40/100. High severity; Remotely exploitable, no login, no user action

Software pages

Drupal vulnerabilities

References

← Back to latest CVEs