dbcve.org
SafariWeb browser · Apple

CVE-2025-43356

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 18.7 / 26.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 handling of caches. This issue is fixed in Safari 26, iOS 18.7 and iPadOS 18.7, iOS 26 and iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. A website may be able to access sensor information without user consent.

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

Improper cache handling in WebKit allows malicious websites to access device sensor information (accelerometer, gyroscope, etc.) without user consent, potentially exposing sensitive motion data to unauthorized web origins.

MitigationDeploy the patched versions (Safari 26, iOS/iPadOS 18.7 or 26, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26) to all affected devices to remediate the vulnerability.

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
SafariWeb browser
Affected:< 26.0
IpadosOperating system
Affected:< 18.7
Iphone OsOperating system
Affected:< 18.7
macOSOperating system
Affected:< 26.0
TvosOperating system
Affected:< 26.0
VisionosOperating system
Affected:< 26.0
WatchosOperating system
Affected:< 26.0

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

CVSS:3.1/AV:N/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 Safari version on macOS
    Open Safari, click Safari > About Safari, or run `defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString` in Terminal
    Affected if Version is below 26.0 and the browser can access device motion sensors
  2. Check macOS version
    Click Apple menu > About This Mac, or run `sw_vers -productVersion` in Terminal
    Affected if macOS version is below 26.0 and Safari (which is bundled) can access device motion sensors
  3. Check iOS or iPadOS version
    Go to Settings > General > About, or connect device to Finder/iTunes and check the software version
    Affected if iOS/iPadOS version is below 18.7 and Safari or any browser using WebKit can access device motion sensors
  4. Check tvOS version
    Go to Settings > General > About > Version, or check via Finder or Xcode
    Affected if tvOS version is below 26.0 and the device runs web content that accesses motion sensors
  5. Check visionOS and watchOS versions
    Go to Settings > General > About on the device
    Affected if visionOS or watchOS version is below 26.0 and web content can access device motion sensors

A device is affected if it runs an Apple OS version below 26.0 (or below 18.7 for iOS/iPadOS) and has web browsers or apps using WebKit that can access motion sensors without user consent.

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

Deploy the patched versions (Safari 26, iOS/iPadOS 18.7 or 26, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26) to all affected devices to remediate the vulnerability.

Recommended fix High confidence

iOS 18.7/iPadOS 18.7, macOS Tahoe 26/Safari 26, tvOS 26, visionOS 26, watchOS 26

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple Watch, Apple TV, or Vision Pro)
  2. Check the current OS version in Settings > General > About (iOS/iPadOS) or System Settings > About (macOS)
  3. For iPhone/iPad: Upgrade to iOS 18.7 and iPadOS 18.7 (or iOS 26/iPadOS 26 for newer devices)
  4. For Mac: Upgrade to macOS Tahoe 26 ( Safari will upgrade to 26.0 automatically)
  5. For Apple TV: Upgrade to tvOS 26
  6. For Vision Pro: Upgrade to visionOS 26
  7. For Apple Watch: Upgrade to watchOS 26
  8. After upgrade, verify the sensor permissions are properly restricted in Safari settings
Caveat Standard Apple OS upgrade considerations apply (backup before upgrade, ensure device meets minimum requirements)

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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