IpadosOperating system · Apple

CVE-2025-43455

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 26.1 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 privacy issue was addressed with improved checks. This issue is fixed in iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1, watchOS 26.1. A malicious app may be able to take a screenshot of sensitive information in embedded views.

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

This is a privacy bypass vulnerability in Apple's platform OSes where a malicious application could capture screenshots of sensitive information displayed within embedded views (such as WebViews, document viewers, or other contained UI elements). The vulnerability stems from insufficient access control checks in the screenshot functionality.

MitigationApply the vendor patches (iOS 26.1, iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1, or watchOS 26.1) to affected devices to enforce proper access controls on screenshot capture for embedded views.

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
VisionosOperating system
Affected:< 26.1
WatchosOperating 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 on iPhone
    Open Settings > General > About on the iPhone and locate the Version field. Record the version number displayed (for example, 25.4 or 26.0)
    Affected if Version is below 26.1 (for example, 25.x.x or 26.0.x)
  2. Check iPadOS version on iPad
    Open Settings > General > About on the iPad and locate the Version field. Record the version number displayed
    Affected if Version is below 26.1 (for example, 25.x.x or 26.0.x)
  3. Check visionOS version on Apple Vision device
    Open Settings > General > About on the Vision Pro device and locate the Version field. Record the version number displayed
    Affected if Version is below 26.1 (for example, 25.x.x or 26.0.x)
  4. Check watchOS version on Apple Watch
    Open the Watch app on the paired iPhone, navigate to My Watch > General > About, and record the watchOS version number shown
    Affected if Version is below 26.1 (for example, 25.x.x or 26.0.x)

The device is affected if it runs any version of iOS, iPadOS, visionOS, or watchOS below 26.1, since the vulnerability permits malicious applications to capture screenshots of sensitive content within embedded views like WebViews or document viewers.

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 the vendor patches (iOS 26.1, iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1, or watchOS 26.1) to affected devices to enforce proper access controls on screenshot capture for embedded views.

Recommended fix Moderate confidence

iOS 26.1, iPadOS 26.1, visionOS 26.1, watchOS 26.1

  1. Back up your device data before upgrading
  2. Update iPhone to iOS 26.1 or later via Settings > General > Software Update
  3. Update iPad to iPadOS 26.1 or later via Settings > General > Software Update
  4. Update Apple Vision to visionOS 26.1 or later via Settings > General > Software Update
  5. Update Apple Watch to watchOS 26.1 or later via the Watch app on iPhone
  6. After updating, verify the update was successful in Settings > General > About
Caveat Standard iOS/tvOS upgrade risks apply - ensure backup 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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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