Skip to main content
CVE-2024-31570VulnerabilityPublished Updated

CVE-2024-31570: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-26.

What to do

AI-suggested

To mitigate CVE-2024-31570, organizations should immediately audit their use of FreeImage libraries, specifically versions 3.4.0 through 3.18.0, and plan for upgrades once patches are released. Until official patches are available, consider the following measures: 1) Restrict or block processing of untrusted or unauthenticated XPM image files to reduce exposure. 2) Employ application-level input validation and sandboxing to isolate image processing components. 3) Monitor network and system logs for anomalous behavior indicative of exploitation attempts, such as unexpected crashes or code execution patterns. 4) Use runtime protections like stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) to mitigate exploitation impact. 5) Engage with vendors or open-source maintainers to obtain timely patches or backported fixes. 6) Educate developers and system administrators about the risks of processing untrusted image formats and encourage secure coding practices. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and attack vector.

Description

libfreeimage in FreeImage 3.4.0 through 3.18.0 has a stack-based buffer overflow in the PluginXPM.cpp Load function via an XPM file.

References

Community reviews

Loading reviews…