dbcve.org
IpadosOperating system · Apple

CVE-2025-46304

MEDIUM · 5.7 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 14.8.4 / 15.7.4 or later.
See remediation →
60/100
Remediation priority · Elevated
No privileges

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
The issue was addressed with improved bounds checks. This issue is fixed in iOS 18.7.5 and iPadOS 18.7.5, iOS 26.2 and iPadOS 26.2, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.2, tvOS 26.2, visionOS 26.2, watchOS 26.2. A malicious HID device may cause an unexpected process crash.

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

This is a bounds check vulnerability in Apple's HID (Human Interface Device) handling subsystem. A malicious or specially crafted HID device can trigger an out-of-bounds access, causing an unexpected process crash. The vulnerability is fixed in the listed iOS, iPadOS, macOS, tvOS, visionOS, and watchOS versions.

MitigationApply the appropriate OS update (iOS 18.7.5/iPadOS 18.7.5 or later, macOS Sequoia 15.7.4/Sonoma 14.8.4 or later, or the 26.2 versions for newer OS releases) to all affected devices. For organizations, inventory all Apple devices and ensure they receive the patched versions.

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.7.5
Iphone OsOperating system
Affected:< 18.7.5
macOSOperating system
Affected:>= 14.0, < 14.8.4>= 15.0, < 15.7.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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/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 checks

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

  1. Check iOS version on iPhone
    Go to Settings > General > About and look at the Version number, or run 'nsver' via Terminal app after enabling Developer mode
    Affected if Version is less than 18.7.5
  2. Check iPadOS version on iPad
    Go to Settings > General > About and look at the Version number, or run 'nsver' via Terminal app after enabling Developer mode
    Affected if Version is less than 18.7.5
  3. Check macOS version
    Run 'sw_vers -productVersion' in Terminal, or go to System Settings > About and look at the macOS version
    Affected if Version is 14.0 to 14.8.3, or 15.0 to 15.7.3
  4. Verify if HID device support is active
    HID support is built into macOS and iOS. On macOS, you can check for HID-related kexts with 'kextstat | grep -i hid' - if any HID-related kernel extensions are loaded, the subsystem is active
    Affected if HID kernel extensions are loaded and the OS version falls within the affected ranges listed above

The device is affected if it runs iOS/iPadOS below 18.7.5 or macOS between 14.0-14.8.3 or 15.0-15.7.3 and has HID device support enabled (which is the default state).

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 14.8.4 / 15.7.4 / 18.7.5 or later
Fixed in 14.8.415.7.418.7.5
Interim mitigation

Apply the appropriate OS update (iOS 18.7.5/iPadOS 18.7.5 or later, macOS Sequoia 15.7.4/Sonoma 14.8.4 or later, or the 26.2 versions for newer OS releases) to all affected devices. For organizations, inventory all Apple devices and ensure they receive the patched versions.

Recommended fix High confidence

iOS 18.7.5/iPadOS 18.7.5 or later; macOS Sonoma 14.8.4 or later; macOS Sequoia 15.7.4 or later

  1. Open Settings > General > Software Update on iPhone or iPad, or System Settings > General > Software Update on Mac
  2. Ensure the device is connected to Wi-Fi and has sufficient battery (or is plugged into power)
  3. Check for and install the available update: iOS 18.7.5/iPadOS 18.7.5 or later for iPhone/iPad; macOS Sonoma 14.8.4 or later, or macOS Sequoia 15.7.4 or later for Mac
  4. Restart the device if prompted to complete the installation
  5. After updating, verify the security update is applied by checking Settings > General > About > Software Version
Caveat Standard Apple security update with minimal risk; may include other cumulative fixes

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46304 — 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-46304 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