Persistent device-lock failure via Siri state mishandling
Published Nov 4, 2025 · Updated Nov 4, 2025
State-management failure in Siri in Apple iOS and iPadOS before 26.1 allows remote attackers to prevent a device from locking. Apple identifies flawed Siri state management but does not disclose the state transition or condition that leaves device locking persistently disabled. No authentication or user interaction is required under CISA's published assessment, and the bounded consequence is persistent failure of the device lock.
Summary
What happened
State-management failure in Siri in Apple iOS and iPadOS before 26.1 allows remote attackers to prevent a device from locking. Apple identifies flawed Siri state management but does not disclose the state transition or condition that leaves device locking persistently disabled. No authentication or user interaction is required under CISA's published assessment, and the bounded consequence is persistent failure of the device lock.
The record
- CVE
- CVE-2025-43454
- Published
- Nov 4, 2025
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-284
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 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 <26.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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