dbcve.org
SafariWeb browser · Apple

CVE-2025-31192

MEDIUM · 6.7 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 15.4 / 18.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable

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 checks. This issue is fixed in Safari 18.4, iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4. 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 · high confidence

This WebKit vulnerability allows malicious websites to access device sensor information (such as accelerometer, gyroscope, or other motion sensors) without obtaining proper user consent. The issue stems from insufficient permission checks in the sensor access API, potentially enabling fingerprinting or surveillance of users through their device's motion data.

MitigationUpdate affected devices to Safari 18.4, iOS 18.4/iPadOS 18.4, or macOS Sequoia 15.4 to receive the improved sensor permission checks. No additional configuration changes are required beyond applying the software updates.

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:< 18.4
IpadosOperating system
Affected:< 18.4
Iphone OsOperating system
Affected:< 18.4
macOSOperating system
Affected:>= 15.0, < 15.4

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

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

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 the Apple product and platform
    Determine if the device runs Safari browser, iOS, iPadOS, or macOS. On macOS, you can check by clicking the Apple menu > About This Mac. On iOS/iPadOS, go to Settings > General > About.
    Affected if Any Apple device running the listed products is a potential target.
  2. Check Safari browser version on macOS
    Open Safari, click Safari menu > About Safari. The version number appears next to Safari.
    Affected if Safari version is less than 18.4 on macOS.
  3. Check iOS version on iPhone
    Open Settings > General > About on the iPhone. The version number is displayed next to Software Version.
    Affected if iOS version is less than 18.4.
  4. Check iPadOS version on iPad
    Open Settings > General > About on the iPad. The version number is displayed next to Software Version.
    Affected if iPadOS version is less than 18.4.
  5. Check macOS version
    Click the Apple menu > About This Mac. The macOS version number (such as 15.0, 15.3, 15.4) is displayed below the macOS name.
    Affected if macOS version is 15.0, 15.1, 15.2, or 15.3 (any version >= 15.0 but < 15.4).

The environment is affected if Safari is below version 18.4, or iOS/iPadOS is below 18.4, or macOS is version 15.0 through 15.3.

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 15.4 / 18.4 or later
Fixed in 15.418.4
Interim mitigation

Update affected devices to Safari 18.4, iOS 18.4/iPadOS 18.4, or macOS Sequoia 15.4 to receive the improved sensor permission checks. No additional configuration changes are required beyond applying the software updates.

Recommended fix High confidence

Safari 18.4, iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4

  1. Check current version: On iPhone/iPad, go to Settings > General > Software Update. On Mac, go to Apple menu > System Settings > General > Software Update. On Safari, check Safari > About Safari.
  2. For iPhone and iPad: Update to iOS 18.4 or iPadOS 18.4 via Settings > General > Software Update.
  3. For macOS: Update to macOS Sequoia 15.4 via System Settings > General > Software Update.
  4. For Safari on older macOS: Update Safari via the macOS update to get Safari 18.4.

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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