CVE-2025-30436
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThis issue was addressed by restricting options offered on a locked device. This issue is fixed in iOS 18.4 and iPadOS 18.4. An attacker may be able to use Siri to enable Auto-Answer Calls.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA vulnerability in iOS and iPadOS allowed Siri to present options on a locked device that should have been restricted, enabling an attacker to enable the Auto-Answer Calls setting without authentication. This bypasses the device lock security model by leveraging Siri's voice interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 18.4< 18.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the iOS or iPadOS version installed on the deviceOn the device, go to Settings > General > About and note the version number. Alternatively, via MDM or Apple Configurator, query the OSVersion or ProductVersion field.Affected if The version is less than 18.4 (for example, 18.3.x, 18.2.x, or any earlier release)
-
Determine if Siri is enabled on the Lock ScreenGo to Settings > Siri & Search > and check if 'Allow Siri When Locked' is turned ON. In MDM, check the com.apple.springboard predicate or Siri settings.Affected if Siri is enabled on the Lock Screen (the vulnerability requires Siri to be accessible from the lock screen)
-
Verify the Auto-Answer Calls setting is accessible without authenticationOn a locked device, activate Siri by saying 'Hey Siri' or pressing the side button, then ask 'Turn on Auto-Answer Calls' or similar to see if Siri can modify this setting without unlocking the device.Affected if Siri can enable or modify the Auto-Answer Calls setting without the device being first unlocked with authentication
The device is affected if it runs iOS/iPadOS versions earlier than 18.4 AND has Siri enabled on the Lock Screen, allowing the Auto-Answer Calls setting to be modified without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped18.4
Deploy iOS 18.4 or iPadOS 18.4 to affected devices to receive the fix. Consider disabling Siri on the lock screen or restricting Auto-Answer Calls via MDM as additional hardening.
iOS 18.4 / iPadOS 18.4
- Back up your iPhone or iPad using iCloud or your computer before updating
- Connect your device to power and ensure it has sufficient battery
- Connect to Wi-Fi network
- Go to Settings > General > Software Update
- Download and install iOS 18.4 (for iPhone) or iPadOS 18.4 (for iPad)
- Restart your device if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30436 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data