Memory corruption via insufficient AppleJPEG bounds checks
Published Dec 12, 2025 · Updated Dec 12, 2025
Out-of-bounds write in AppleJPEG in Apple macOS allows remote attackers to corrupt memory by inducing processing of a crafted file. AppleJPEG performs insufficient bounds checks while processing file data, allowing a write outside the intended memory buffer; Apple has not disclosed the affected parser or boundary calculation. User interaction is required, and the published impact is memory corruption rather than a confirmed code-execution outcome.
Summary
What happened
Out-of-bounds write in AppleJPEG in Apple macOS allows remote attackers to corrupt memory by inducing processing of a crafted file. AppleJPEG performs insufficient bounds checks while processing file data, allowing a write outside the intended memory buffer; Apple has not disclosed the affected parser or boundary calculation. User interaction is required, and the published impact is memory corruption rather than a confirmed code-execution outcome.
The record
- CVE
- CVE-2025-43539
- Published
- Dec 12, 2025
- Updated
- Dec 12, 2025
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-119, CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2025CVE publishedPublication date reported by the CVE source.
- Dec 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <14.8
- Affected versionversion=unspecified <15.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo