Physical Login Window bypass during software update
Published Dec 20, 2024 · Updated Apr 2, 2026
Improper state management in Apple macOS Sequoia before 15.1 allows physically proximate attackers to bypass Login Window during an update. Apple identifies deficient Login Window state management during software updates but has not disclosed the affected state transition or code path. Exploitation requires physical access during an active update and bypasses local login authentication; no remote effect is reported.
Summary
What happened
Improper state management in Apple macOS Sequoia before 15.1 allows physically proximate attackers to bypass Login Window during an update. Apple identifies deficient Login Window state management during software updates but has not disclosed the affected state transition or code path. Exploitation requires physical access during an active update and bypasses local login authentication; no remote effect is reported.
The record
- CVE
- CVE-2024-44231
- Published
- Dec 20, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- Unavailable
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 20, 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 <15.1
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
No sourced classifications are available.
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