CVE-2026-87768

DateTime::Lite versions before 0.8.1 for Perl allow CPU exhaustion via a per-day loop when adding seconds

Published Oct 30, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
DateTime::Lite versions before 0.8.1 for Perl allow CPU exhaustion via a per-day loop when adding seconds.

_normalize_leap_seconds crosses day boundaries one day at a time, so add(seconds => $n) on an object with a non-floating time zone takes about |$n|/86400 iterations, and nothing limits $n. The XS implementation and the pure-Perl fallback both have the loop.

An attacker who controls the number of seconds added can keep the process busy for as long as they choose.

Analysis

AI-generated

Technical impact

The vulnerability arises when DateTime::Lite uses a per‑day loop to normalize leap seconds. The add(seconds => $n) routine iterates once for every 86,400 seconds in the value of $n, and the routine has no upper bound. An attacker who can influence the seconds value can therefore cause the module to run for an arbitrarily long time, exhausting CPU resources. The result is a denial‑of‑service condition, where legitimate processes or the host system may become unresponsive.

Affected Systems

Perl applications that depend on the DateTime::Lite CPAN module with a version earlier than 0.8.1 are vulnerable. The vulnerability is present in all pre‑0.8.1 releases run with the XS implementation and the pure‑Perl fallback.

Risk and Exploitability

Because the loop has no built‑in rate limiting, the condition can be triggered with a single call that supplies a large seconds argument. There's no network or remote trigger described, so exploitation requires control of the add(seconds) parameter from within the application. The CVSS score of 7.5 indicates a high severity flaw, and the EPSS score of less than 1% denotes a low probability of exploitation. The lack of a defensive guard makes the flaw a high‑impact denial‑of‑service vector. The vulnerability is not currently listed in the CISA KEV catalog.

Remediation

Vendor Solution

Upgrade to DateTime-Lite v0.8.1 or later.


OpenCVE Recommended Actions

  • Upgrade to DateTime::Lite v0.8.1 or newer.
  • Validate or constrain the seconds argument before calling add to prevent excessive loops.
  • Monitor CPU usage of the affected process and terminate it if usage exceeds normal thresholds.

Generated by OpenCVE AI on November 6, 2026 at 19:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
First Time appeared Perl
Perl datetime::lite
Vendors & Products Perl
Perl datetime::lite
Type Values Removed Values Added
Description DateTime::Lite versions before 0.8.1 for Perl allow CPU exhaustion via a per-day loop when adding seconds. _normalize_leap_seconds crosses day boundaries one day at a time, so add(seconds => $n) on an object with a non-floating time zone takes about |$n|/86400 iterations, and nothing limits $n. The XS implementation and the pure-Perl fallback both have the loop. An attacker who controls the number of seconds added can keep the process busy for as long as they choose.
Title DateTime::Lite versions before 0.8.1 for Perl allow CPU exhaustion via a per-day loop when adding seconds
Weaknesses CWE-407
References
Weaknesses
  • CWE-407

    Inefficient Algorithmic Complexity

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 6, 2026, 4:37 PM
Reserved
Sep 9, 2026, 8:09 AM
Status
Deferred
Published
Oct 30, 2026, 1:20 PM
Modified
Nov 6, 2026, 5:20 PM