Skip to main content
VulnerabilityPublished

CVE-2026-87768: DateTime-Lite (Perl module) · Inefficient Algorithmic Complexity

Affects DateTime-Lite (Perl module)Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to 0.8.1 when convenient.

Data as of 30 Oct 2026, 12:33 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 0.8.1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade DateTime-Lite (Perl module) to 0.8.1.

Affected software

ProductAffectedFixed in
DateTime-LiteAffected
  • <0.8.1
Fixed in
  • 0.8.1
CPANDateTime-Litepkg:cpan/DateTime-LiteOther threatsAffected
  • <0.8.1
Fixed in
  • 0.8.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…