CVE-2024-53901: n/a
Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium · fixed in 1.025 : update affected systems when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.025
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2024
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 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2024-53901, organizations should: 1) Monitor for the release of Perl Imager version 1.025 or later that addresses this vulnerability and apply the update promptly. 2) Implement strict input validation and sanitization on all images processed by the trim() method to prevent malformed or malicious inputs. 3) Restrict access to systems and applications using the Perl Imager package to trusted users to reduce the risk of local exploitation. 4) Employ runtime protections such as heap overflow detection tools or memory safety mechanisms where feasible. 5) Conduct code reviews and testing focused on image processing functions to identify similar vulnerabilities. 6) Educate developers and system administrators about the risks of processing untrusted image data and encourage secure coding practices. 7) If immediate patching is not possible, consider isolating or sandboxing the image processing components to limit the impact of potential crashes.
Description
The Imager package before 1.025 for Perl has a heap-based buffer overflow leading to denial of service, or possibly unspecified other impact, when the trim() method is called on a crafted input image.