IpadosOperating system · Apple

CVE-2025-46305

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 · moderate confidence

A bounds check vulnerability in Apple's HID (Human Interface Device) handling subsystem allows a malicious HID device to trigger an unexpected process crash. The issue was addressed with improved bounds checks in the affected operating systems.

MitigationApply the available security updates: iOS 18.7.5/iPadOS 18.7.5, iOS 26.2/iPadOS 26.2, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.2, tvOS 26.2, visionOS 26.2, and watchOS 26.2.

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
    On the iPhone, go to Settings > General > About > Version to view the installed iOS version
    Affected if The installed iOS version is below 18.7.5
  2. Check iPadOS version on iPad
    On the iPad, go to Settings > General > About > Version to view the installed iPadOS version
    Affected if The installed iPadOS version is below 18.7.5
  3. Check macOS version
    Click the Apple menu > About This Mac to view the installed macOS version and release number
    Affected if The installed macOS version is 14.0 through 14.8.3, or 15.0 through 15.7.3
  4. Check if HID device support is active
    Verify that Bluetooth or USB peripheral support is enabled on the device (Settings > Bluetooth on iOS, System Preferences > Bluetooth or System Settings > Bluetooth on macOS)
    Affected if The device has Bluetooth or USB HID device support enabled and can accept connections from external input devices

A device is affected if it runs iOS/iPadOS below 18.7.5 or macOS in the ranges 14.0-14.8.3 or 15.0-15.7.3, and has the ability to accept connections from external HID devices.

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 available security updates: iOS 18.7.5/iPadOS 18.7.5, iOS 26.2/iPadOS 26.2, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.2, tvOS 26.2, visionOS 26.2, and watchOS 26.2.

Recommended fix High confidence

iOS 18.7.5 / iPadOS 18.7.5 / macOS Sonoma 14.8.4 / macOS Sequoia 15.7.4 (or respective 26.2 releases)

  1. For iPhone: Navigate to Settings > General > Software Update and update to iOS 18.7.5 (or iOS 26.2 if available in your region)
  2. For iPad: Navigate to Settings > General > Software Update and update to iPadOS 18.7.5 (or iPadOS 26.2 if available in your region)
  3. For macOS Sonoma (14.x): Go to System Settings > General > Software Update and update to macOS Sonoma 14.8.4
  4. For macOS Sequoia (15.x): Go to System Settings > General > Software Update and update to macOS Sequoia 15.7.4
  5. After updating, verify the OS version reflects the fixed release in Settings > General > About
Caveat Standard OS update risks apply - ensure backups exist before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46305 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