CVE-2025-31229
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 · uneditedA logic issue was addressed with improved checks. This issue is fixed in iOS 18.6 and iPadOS 18.6. Passcode may be read aloud by VoiceOver.
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 · high confidenceA logic flaw in iOS VoiceOver accessibility feature allowed the screen reader to audibly announce passcode characters during device unlock, exposing sensitive authentication credentials to unauthorized listeners.
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.6< 18.6CVSS 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.
-
Confirm VoiceOver is enabledGo to Settings > Accessibility > VoiceOver, or ask Siri 'Is VoiceOver on?'Affected if VoiceOver is currently enabled on the device - this is required for the vulnerability to apply
-
Check iOS or iPadOS versionGo to Settings > General > About and note the software version numberAffected if Version is earlier than 18.6 (for example, 18.5.x, 18.4.x, 17.x, etc.) - versions before 18.6 contain the flawed VoiceOver logic
-
Verify VoiceOver speaks passwords settingGo to Settings > Accessibility > VoiceOver > Speech > Speak Passwords (or inspect VoiceOver verbosity settings)Affected if Password speaking is enabled and VoiceOver is active, the passcode characters would be announced audibly during unlock attempts
Device is affected if VoiceOver is enabled AND the installed iOS/iPadOS version is earlier than 18.6, allowing passcode characters to be audibly announced during device unlock.
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.6
Update affected iPhones and iPads to iOS 18.6 or iPadOS 18.6 which contains the corrected logic checks for VoiceOver passcode handling.
iOS 18.6 / iPadOS 18.6
- Back up your device data before updating
- Navigate to Settings > General > Software Update on your iPhone or iPad
- Download and install iOS 18.6 or later (for iPhone) or iPadOS 18.6 or later (for iPad)
- After updating, verify the fix by testing VoiceOver functionality to confirm passcode is no longer read aloud
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31229 — 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-31229 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