CVE-2025-24198
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, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An attacker with physical access may be able to use Siri to access sensitive user data.
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 confidenceThis is a physical access vulnerability in Apple's Siri voice assistant where an attacker with physical access to a locked iPhone, iPad, or Mac could invoke Siri to bypass lock screen protections and access sensitive user data. The vulnerability was addressed by restricting the options and actions available when Siri is invoked on a locked device.
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< 17.7.6>= 18.0, < 18.4< 18.4>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 iOS or iPadOS versionOpen Settings > General > About and note the version number (for example, 18.3.1 or 17.5). Compare this to the affected ranges: iPadOS < 17.7.6 or >= 18.0 but < 18.4; iOS < 18.4.Affected if The installed version falls within any of the affected ranges (iPadOS: < 17.7.6, >= 18.0 to < 18.4; iPhone: < 18.4).
-
Check macOS versionOpen System Settings (or System Preferences) > About and note the version number (for example, 14.3.2 or 13.6.1). Compare this to the affected ranges: >= 13.0 but < 13.7.5; >= 14.0 but < 14.7.5; >= 15.0 but < 15.4.Affected if The installed version falls within any of the affected ranges (13.0-13.7.4, 14.0-14.7.4, or 15.0-15.3).
-
Verify if Siri is enabled on the lock screenOn iOS/iPadOS: go to Settings > Face ID & Passcode (or Touch ID & Passcode) and check if 'Siri' is turned ON under 'Allow Access When Locked'. On macOS: go to System Settings > Lock Screen and check if Siri is accessible without logging in.Affected if The device is running an affected OS version AND Siri is enabled and accessible from the lock screen, meaning anyone with physical access could invoke Siri on the locked device.
A device is affected if it runs an iOS/iPadOS version below 18.4 (or iPadOS 17.7.6 for iPad), or a macOS version below 13.7.5/14.7.5/15.4, AND has Siri access permitted on the lock screen.
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 · scoped13.7.514.7.515.4
Apply the available security updates (iOS 18.4, iPadOS 17.7.6/18.4, macOS Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4) to all affected devices. As a defense-in-depth measure, consider disabling Siri access on the lock screen via MDM or device settings.
iOS 18.4 / iPadOS 18.4 / iPadOS 17.7.6 / macOS Ventura 13.7.5 / macOS Sonoma 14.7.5 / macOS Sequoia 15.4
- Identify your current iOS/iPadOS/macOS version from Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
- Determine which upgrade path applies: iPadOS 17.x users should upgrade to 17.7.6, iPadOS 18.x users should upgrade to 18.4, iPhone OS users should upgrade to 18.4
- For macOS Ventura (13.x), upgrade to 13.7.5; for macOS Sonoma (14.x), upgrade to 14.7.5; for macOS Sequoia (15.x), upgrade to 15.4
- Back up important data before applying the update as a precaution
- Install the update via Settings > General > Software Update (iOS/iPadOS) or System Settings > General > Software Update (macOS)
- Verify the update was successful by checking the version number in Settings/About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24198 — 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-24198 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