CVE-2024-25448: feh · Out-of-bounds Write
Affects fehSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Feb 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubderf/fehpkg:github/derf/fehOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately audit all systems and applications using imlib2 version 1.9.1 or earlier to identify vulnerable instances.
- Avoid processing untrusted or unauthenticated image files with imlib2 until a patch is available.
- Implement strict input validation and sandboxing for image processing components to limit the impact of potential exploitation.
- Monitor security advisories from imlib2 maintainers and apply patches promptly once released.
- Employ application-layer protections such as antivirus and endpoint detection to detect anomalous behavior triggered by exploitation attempts.
- Educate users about the risks of opening images from untrusted sources to reduce the likelihood of user interaction-based exploitation.
- Consider using alternative, more secure image processing libraries if immediate patching is not feasible.
- Deploy network-level controls to block or inspect suspicious image traffic where possible.
- Incorporate runtime application self-protection (RASP) or exploit mitigation technologies like ASLR and DEP to reduce exploitation success.
Description
An issue in the imlib_free_image_and_decache function of imlib2 v1.9.1 allows attackers to cause a heap buffer overflow via parsing a crafted image.