Skip to main content
CVE-2024-44142VulnerabilityPublished Updated

CVE-2024-44142: Apple GarageBand · Processing a maliciously crafted image may lead to arbitrary code execution

Affects Apple GarageBandSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in 10.4.12 : patch Apple GarageBand soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.4.12
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2025

  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

Affected software

ProductAffectedFixed in
Apple GarageBandAffected
  • =0
Fixed in–

AI-suggested

1. Immediately update GarageBand to version 10.4.12 or later, which contains the fix for this vulnerability. 2. Educate users to avoid opening GarageBand projects or image files from untrusted or unknown sources. 3. Implement endpoint security solutions that can detect and block suspicious file activities related to GarageBand. 4. Use macOS security features such as Gatekeeper and XProtect to reduce the risk of executing malicious code. 5. Restrict user permissions to limit the impact of potential exploitation, especially on shared or multi-user systems. 6. Monitor system logs and network traffic for unusual behavior indicative of exploitation attempts. 7. For organizations, consider application whitelisting and sandboxing GarageBand usage to contain potential threats. 8. Regularly back up important data to enable recovery in case of compromise.

Description

The issue was addressed with improved bounds checks. This issue is fixed in GarageBand 10.4.12. Processing a maliciously crafted image may lead to arbitrary code execution.

References

Community reviews

Loading reviews…