dbcve.org
IpadosOperating system · Apple

CVE-2025-31220

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 13.7.6 / 14.7.6 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 privacy issue was addressed by removing sensitive data. This issue is fixed in iPadOS 17.7.7, macOS Sequoia 15.5, macOS Sonoma 14.7.6, macOS Ventura 13.7.6. A malicious app may be able to read sensitive location information.

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 local privacy bypass vulnerability in Apple's iOS/macOS where a malicious application could improperly access sensitive location information. The vulnerability existed in the operating system's handling of location data, likely allowing a non-privileged or sandboxed app to read location data it should not have access to.

MitigationApply the relevant OS patch: iPadOS 17.7.7, macOS Sequoia 15.5, macOS Sonoma 14.7.6, or macOS Ventura 13.7.6. Ensure devices are updated through standard patch management processes.

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:< 17.7.7
macOSOperating system
Affected:< 13.7.6>= 14.0, < 14.7.6>= 15.0, < 15.5

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. Identify the iPadOS version
    Go to Settings > General > About on the iPad and note the version number. Compare it to the affected range: versions before 17.7.7 are vulnerable.
    Affected if The iPadOS version is less than 17.7.7
  2. Identify the macOS version
    Click the Apple menu > About This Mac and note the version number. Compare it to the affected ranges: versions before 13.7.6, or between 14.0 and 14.7.5, or between 15.0 and 15.4 are vulnerable.
    Affected if The macOS version falls into any of the affected ranges: < 13.7.6, >= 14.0 and < 14.7.6, or >= 15.0 and < 15.5
  3. Verify location services status
    On iPad: Settings > Privacy & Security > Location Services. On macOS: System Settings > Privacy & Security > Location Services. Check if the service is enabled.
    Affected if Location services are enabled on a device running an affected OS version
  4. Review granted location permissions
    On iPad: Settings > Privacy & Security > Location Services to see which apps have permission. On macOS: System Settings > Privacy & Security > Location Services to review app permissions.
    Affected if Any third-party apps have location permission granted on a device running an affected OS version

A user is affected if their device runs iPadOS before 17.7.7 or macOS before the patched versions (13.7.6, 14.7.6, or 15.5) and has location services enabled with granted app permissions.

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 13.7.6 / 14.7.6 / 15.5 or later
Fixed in 13.7.614.7.615.5
Interim mitigation

Apply the relevant OS patch: iPadOS 17.7.7, macOS Sequoia 15.5, macOS Sonoma 14.7.6, or macOS Ventura 13.7.6. Ensure devices are updated through standard patch management processes.

Recommended fix High confidence

iPadOS 17.7.7; macOS Ventura 13.7.6; macOS Sonoma 14.7.6; macOS Sequoia 15.5

  1. On the affected device, go to Settings > General > Software Update to check for and install the available update
  2. For iPadOS devices: Upgrade to iPadOS 17.7.7 or later
  3. For macOS Ventura (13.x) devices: Upgrade to macOS Ventura 13.7.6 or later
  4. For macOS Sonoma (14.x) devices: Upgrade to macOS Sonoma 14.7.6 or later
  5. For macOS Sequoia (15.x) devices: Upgrade to macOS Sequoia 15.5 or later
  6. Alternatively, on Mac go to Apple menu > System Settings > General > Software Update to install the update
Caveat Standard macOS/iPadOS point releases typically have minimal breaking changes; ensure critical apps are compatible 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
  • 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-31220 — 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-31220 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