IpadosOperating system · Apple

CVE-2025-43295

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 14.8 / 15.7 or later.
See remediation →
58/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
A denial-of-service issue was addressed with improved validation. This issue is fixed in iOS 18.7 and iPadOS 18.7, macOS Sequoia 15.7, macOS Sonoma 14.8, macOS Tahoe 26. An app may be able to cause a denial-of-service.

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 denial-of-service vulnerability in Apple operating systems that was addressed with improved input validation. The issue allows a malicious app to potentially cause a system crash or service unavailability. Affected versions include iOS 18.7, iPadOS 18.7, macOS Sequoia 15.7, macOS Sonoma 14.8, and macOS Tahoe 26.

MitigationUpdate affected devices to iOS 18.7/iPadOS 18.7 or macOS 15.7/14.8/26 or later. For enterprise environments, deploy updates via MDM and verify completion.

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
Iphone OsOperating system
Affected:< 18.7
macOSOperating system
Affected:>= 14.0, < 14.8>= 15.0, < 15.7

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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. Identify your Apple device type
    Determine if the device is an iPhone, iPad, or Mac. On iOS/iPadOS, go to Settings > General > About. On macOS, click the Apple menu > About This Mac.
    Affected if Device is an iPhone, iPad, or Mac running an affected operating system
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number displayed next to 'Version'.
    Affected if Version is lower than 18.7 (for example, 18.6.x or earlier)
  3. Check macOS version
    On Mac, click the Apple menu > About This Mac. The version number appears below the macOS name (for example, 15.6, 14.7, etc.).
    Affected if Version is 15.0 to 15.6.x (affected in macOS Sequoia) or 14.0 to 14.7.x (affected in macOS Sonoma)
  4. Verify macOS Tahoe version if applicable
    If the Mac is running a newer macOS release named Tahoe, check the version in About This Mac.
    Affected if Version is lower than 26 (the fixed release for macOS Tahoe)

You are affected if your device runs iOS or iPadOS versions earlier than 18.7, or macOS versions 14.0-14.7.x or 15.0-15.6.x, or any macOS Tahoe version earlier than 26.

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 / 15.7 / 18.7 or later
Fixed in 14.815.718.7
Interim mitigation

Update affected devices to iOS 18.7/iPadOS 18.7 or macOS 15.7/14.8/26 or later. For enterprise environments, deploy updates via MDM and verify completion.

Recommended fix High confidence

iOS 18.7, iPadOS 18.7, macOS Sonoma 14.8, or macOS Sequoia 15.7 depending on device

  1. For iOS devices: Go to Settings > General > Software Update and install iOS 18.7
  2. For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 18.7
  3. For macOS Sonoma (14.x) devices: Go to System Settings > General > Software Update and install macOS Sonoma 14.8
  4. For macOS Sequoia (15.x) devices: Go to System Settings > General > Software Update and install macOS Sequoia 15.7
  5. After updating, verify the version in Settings > General > About to confirm the update was successful

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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