dbcve.org
macOSOperating system · Apple

CVE-2025-31240

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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
This issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.5, macOS Sonoma 14.7.6, macOS Ventura 13.7.6. Mounting a maliciously crafted AFP network share may lead to system termination.

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 denial of service vulnerability exists in macOS AFP (Apple Filing Protocol) client implementation. An attacker can craft a malicious AFP network share that, when mounted by a victim, triggers system termination. The fix involves improved input validation checks on AFP share handling.

MitigationApply the vendor-supplied security updates: macOS Sequoia 15.5, macOS Sonoma 14.7.6, or macOS Ventura 13.7.6 depending on the installed version.

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

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

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 installed macOS version
    Run 'sw_vers -productVersion' in Terminal to get the exact version number
    Affected if The version is less than 13.7.6, or between 14.0 and 14.7.5, or between 15.0 and 15.4
  2. Verify macOS release name
    Run 'sw_vers -productName' to confirm whether the system is running Ventura, Sonoma, or Sequoia
    Affected if Running Ventura below 13.7.6, Sonoma below 14.7.6, or Sequoia below 15.5
  3. Check if AFP client is active
    Run 'ps aux | grep -i applefileserver' to see if the Apple Filing Protocol daemon is running
    Affected if The AFP daemon is running and the version falls within the affected ranges above
  4. Identify mounted AFP shares
    Run 'mount' or 'df -t afp' in Terminal to list any currently mounted AFP network shares
    Affected if Any AFP shares are mounted and the macOS version is in the affected range

The system is vulnerable if the installed macOS version is below 13.7.6 (Ventura), below 14.7.6 (Sonoma), or below 15.5 (Sequoia), especially if AFP functionality is in use.

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 vendor-supplied security updates: macOS Sequoia 15.5, macOS Sonoma 14.7.6, or macOS Ventura 13.7.6 depending on the installed version.

Recommended fix High confidence

macOS Ventura 13.7.6, macOS Sonoma 14.7.6, or macOS Sequoia 15.5

  1. 1. Check the current macOS version by clicking the Apple menu and selecting 'About This Mac'
  2. 2. If running macOS Ventura (13.x), upgrade to version 13.7.6 or later
  3. 3. If running macOS Sonoma (14.x), upgrade to version 14.7.6 or later
  4. 4. If running macOS Sequoia (15.x), upgrade to version 15.5 or later
  5. 5. Use Software Update (System Settings > General > Software Update) to install the security update
Caveat Point release upgrades typically have minimal breaking changes; however, ensure critical applications are compatible before updating

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

Fix this in macOS 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-31240 — 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-31240 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