dbcve.org
IpadosOperating system · Apple

CVE-2025-43426

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
A logging issue was addressed with improved data redaction. This issue is fixed in iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1. An app may be able to access sensitive user data.

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 logging vulnerability in iOS 26.1, iPadOS 26.1, and macOS Tahoe 26.1 allowed sensitive user data to be written to logs without proper redaction, potentially exposing this data to other apps through log access.

MitigationApply iOS 26.1, iPadOS 26.1, or macOS Tahoe 26.1 (or later) to receive the corrected logging with improved data redaction.

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:< 26.1
Iphone OsOperating system
Affected:< 26.1

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 installed
    On the iOS device, go to Settings > General > About > Version. Note the version number displayed.
    Affected if The version shown is earlier than 26.1 (for example, 26.0, 25.x, or earlier).
  2. Check iPadOS version installed
    On the iPad device, go to Settings > General > About > Version. Note the version number displayed.
    Affected if The version shown is earlier than 26.1.
  3. Check version via MDM or device management tool
    If devices are managed via MDM (Mobile Device Management), query the device inventory or software inventory report to retrieve the iOS/iPadOS version for enrolled devices.
    Affected if Any managed device reports an iOS or iPadOS version less than 26.1.
  4. Check macOS Tahoe version for related exposure
    On Mac devices, go to System Settings > General > About, or run 'sw_vers' in Terminal, to check the macOS version.
    Affected if The macOS version is earlier than 26.1 and the device syncs with iOS/iPad devices that may expose logs.

A device is affected if it runs iOS or iPadOS version lower than 26.1, as the logging vulnerability existed in those earlier versions and was fixed in 26.1.

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 26.1 or later
Fixed in 26.1
Interim mitigation

Apply iOS 26.1, iPadOS 26.1, or macOS Tahoe 26.1 (or later) to receive the corrected logging with improved data redaction.

Recommended fix High confidence

iOS 26.1 and iPadOS 26.1

  1. Back up your iPhone or iPad device before updating
  2. Open Settings > General > Software Update on the device
  3. Download and install iOS 26.1 (for iPhone) or iPadOS 26.1 (for iPad)
  4. Verify the update was successfully applied by checking Settings > General > About > Version
Caveat Standard iOS/iPadOS update considerations apply - review release notes for any app compatibility 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-43426 — 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-43426 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