dbcve.org
IpadosOperating system · Apple

CVE-2025-30430

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 15.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
This issue was addressed through improved state management. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, watchOS 11.4. Password autofill may fill in passwords after failing authentication.

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 confidence

A state management vulnerability in Apple's password autofill mechanism allows passwords to be automatically filled even after authentication has failed. This creates a critical authentication bypass where the autofill feature does not properly validate the authentication state before populating credentials.

MitigationUpdate all affected Apple devices to iOS 18.4/iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, or watchOS 11.4. For enterprise environments, ensure patch management systems deploy these updates across all managed devices.

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
IpadosOperating system
Affected:< 18.4
Iphone OsOperating system
Affected:< 18.4
macOSOperating system
Affected:>= 15.0, < 15.4
VisionosOperating system
Affected:< 2.4

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS version
    Go to Settings > General > About and look at the Software Version field. Alternatively, use Finder (iTunes) or run 'nsget -ipccommand DeviceInfo' via idevicesyslog on a connected device.
    Affected if The version is less than 18.4 (e.g., 18.3.x, 18.2.x, earlier) AND password autofill is enabled in Settings > Passwords > Password Options.
  2. Check iPadOS version
    Go to Settings > General > About and look at the Software Version field. On Mac, you can also check via Finder or idevicesyslog.
    Affected if The version is less than 18.4 AND password autofill is enabled in Settings > Passwords > Password Options.
  3. Check macOS version
    Click the Apple menu > About This Mac. The version number appears below the macOS name. You can also run 'sw_vers' in Terminal.
    Affected if The version is 15.0, 15.1, 15.2, or 15.3 (any version >= 15.0 but < 15.4) AND password autofill is enabled in System Settings > Passwords > Password Options.
  4. Check visionOS version
    Go to Settings > About. The version is listed under visionOS version. You can also check via Xcode device info.
    Affected if The version is less than 2.4 AND password autofill is enabled in Settings > Passwords > Password Options.

You are affected if your device runs any version less than the fixed release (iOS/iPadOS 18.4, macOS 15.4, visionOS 2.4) AND has password autofill functionality enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.4 / 15.4 / 18.4 or later
Fixed in 2.415.418.4
Interim mitigation

Update all affected Apple devices to iOS 18.4/iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, or watchOS 11.4. For enterprise environments, ensure patch management systems deploy these updates across all managed devices.

Recommended fix High confidence

iOS 18.4 / iPadOS 18.4 / macOS Sequoia 15.4 / visionOS 2.4

  1. Back up your device data before performing any system update
  2. Update iPhone or iPad to iOS 18.4 or iPadOS 18.4 via Settings > General > Software Update
  3. Update Mac running macOS Sequoia to version 15.4 via System Settings > General > Software Update
  4. Update Apple Vision Pro to visionOS 2.4 via Settings > General > Software Update
  5. After updating, verify the password autofill feature works correctly and test authentication flows
Caveat Standard minor OS update risks - review Apple release notes for any behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30430 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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