CVE-2026-14454: Libimager perl · Imager versions before 1.033 for Perl treat unsigned EXIF IFD entry counts as signed
Affects libimager-perlSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libimager-perlpkg:deb/ubuntu/libimager-perl?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlibimager-perlpkg:deb/ubuntu/libimager-perl?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10libimager-perlpkg:deb/ubuntu/libimager-perl?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibimager-perlpkg:deb/ubuntu/libimager-perl?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlibimager-perlpkg:deb/ubuntu/libimager-perl?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSlibimager-perlpkg:deb/ubuntu/libimager-perl?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Imager versions before 1.033 for Perl treat unsigned EXIF IFD entry counts as signed. Imager mishandled large EXIF IFD entry count values, treating them as negative numbers. This could lead to an attempt to allocate a block nearly the size of the address space, which fails and kills the process. An attacker could craft an image with EXIF data that terminates a worker process.