CVE-2026-14454: Imager versions before 1.033 for Perl treat unsigned EXIF IFD entry counts as signed

Published Jul 8, 2026
·
Updated

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.

Affected Software

2 affected components
Imager Perl<1.033
Tonycoz Imager Perl<1.033

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Imager (Perl) to a version that resolves this vulnerability.

    Fixed in 1.033
  2. Compensating control

    Mitigate the impact by restarting/isolating the affected worker process until the Imager upgrade to version 1.033 or later is applied, since the flaw can kill the process during image parsing.

Event History

Jul 8, 2026
CVE Published
via MITRE·12:30 PM
Data Sourced
via MITRE·12:30 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·01:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-14454?

CVE-2026-14454 has a risk rating of 26.

2

What vulnerabilities are associated with CVE-2026-14454?

CVE-2026-14454 is associated with the mishandling of unsigned EXIF IFD entry counts in Imager versions prior to 1.033.

3

How does CVE-2026-14454 affect Imager for Perl?

CVE-2026-14454 affects Imager for Perl by causing the software to treat unsigned EXIF IFD entry counts as signed, which can lead to severe memory allocation issues.

4

How do I fix CVE-2026-14454?

To fix CVE-2026-14454, you should upgrade to Imager version 1.033 or later.

5

What happens if CVE-2026-14454 is not mitigated?

If CVE-2026-14454 is not mitigated, it can result in process termination due to failed memory allocation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203