Gatekeeper bypass via crafted ZIP archive
Published Jul 29, 2024 · Updated Apr 2, 2026
Authentication bypass in Apple macOS before 14.4 allows attackers to evade Gatekeeper checks through a maliciously crafted ZIP archive. Apple identifies libarchive as the affected component but has not published the precise check that fails during ZIP processing. Exploitation requires user interaction with the crafted archive, and the resulting bypass removes Gatekeeper's trust check for contained software.
Summary
What happened
Authentication bypass in Apple macOS before 14.4 allows attackers to evade Gatekeeper checks through a maliciously crafted ZIP archive. Apple identifies libarchive as the affected component but has not published the precise check that fails during ZIP processing. Exploitation requires user interaction with the crafted archive, and the resulting bypass removes Gatekeeper's trust check for contained software.
The record
- CVE
- CVE-2024-27853
- Published
- Jul 29, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-290, T1553.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record 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=0 <14.4
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.
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