CVE-2025-46303
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 · uneditedThe 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 confidenceThis is a denial-of-service vulnerability in Apple's HID (Human Interface Device) stack. A malicious HID device can trigger an out-of-bounds memory access due to insufficient bounds checking, causing an unexpected process crash. The issue affects multiple Apple operating systems and was addressed with improved bounds checks in the specified 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< 18.7.5< 18.7.5< 14.8.4>= 15.0, < 15.7.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhoneGo to Settings > General > About on the device and note the version number (e.g., 18.7, 18.7.4)Affected if The version is lower than 18.7.5 (e.g., 18.7, 18.7.1-18.7.4)
-
Check iPadOS version on iPadGo to Settings > General > About on the device and note the version numberAffected if The version is lower than 18.7.5 (e.g., 18.7, 18.7.1-18.7.4)
-
Check macOS version on MacOpen System Settings > About or run `sw_vers` in Terminal and note the version (e.g., 14.8, 15.6, 15.7)Affected if The version is 14.8.3 or earlier, OR 15.0 through 15.7.3 (any version below 14.8.4 or below 15.7.4, excluding 15.0)
You are affected if your device runs iOS/iPadOS below 18.7.5, or macOS below 14.8.4 (Sonoma) or below 15.7.4 (Sequoia).
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 · scoped14.8.415.7.418.7.5
Apply the vendor-supplied patches: 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, or watchOS 26.2 depending on the affected device.
iOS 18.7.5/iPadOS 18.7.5 or macOS Sonoma 14.8.4/macOS Sequoia 15.7.4
- Identify the current iOS, iPadOS, or macOS version on the affected device via Settings > General > About (iOS/iPadOS) or System Settings > About (macOS)
- For iPhone or iPad: Go to Settings > General > Software Update and install iOS 18.7.5 or iPadOS 18.7.5
- For macOS Sonoma (14.x): Go to System Settings > Software Update and install macOS Sonoma 14.8.4
- For macOS Sequoia (15.x): Go to System Settings > Software Update and install macOS Sequoia 15.7.4
- After updating, verify the fix by checking Settings > General > About shows the correct version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46303 — 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-46303 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