CVE-2024-44915: irfanview · n/a
Affects irfanviewSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 28 Aug 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubyuhano/irfanviewpkg:github/yuhano/irfanviewOther 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
To mitigate CVE-2024-44915, organizations should implement the following specific measures: 1) Avoid opening EXR files from untrusted or unknown sources until a security patch is released; 2) Employ application whitelisting and restrict the use of IrfanView to trusted users and environments; 3) Use sandboxing or isolated virtual machines for opening potentially risky image files to contain crashes and prevent broader system impact; 4) Monitor user activity and logs for repeated crashes or abnormal behavior related to IrfanView; 5) Educate users about the risks of opening unsolicited image files, especially EXR format; 6) Regularly check for updates from IrfanView and apply patches promptly once available; 7) Consider alternative image viewers with robust security track records for handling EXR files in sensitive environments; 8) Implement endpoint protection solutions that can detect and block attempts to exploit application vulnerabilities. These targeted steps go beyond generic advice by focusing on controlling file sources, isolating risky operations, and user awareness.
Description
An issue in the component EXR!ReadEXR+0x4eef0 of Irfanview v4.67.1.0 allows attackers to cause an access violation via a crafted EXR file. This vulnerability can lead to a Denial of Service (DoS).