CVE-2025-31246
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 · uneditedThe issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.5, macOS Sonoma 14.7.6. Connecting to a malicious AFP server may corrupt kernel memory.
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 confidenceA memory handling vulnerability in macOS AFP client allows a malicious AFP server to corrupt kernel memory during connection, potentially leading to privilege escalation or denial of service.
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< 14.7.6>= 15.0, < 15.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed macOS versionRun 'sw_vers -productVersion' in Terminal to get the exact version numberAffected if Version is less than 14.7.6, OR version is 15.0, 15.1, 15.2, 15.3, or 15.4 (any version >= 15.0 but < 15.5)
-
Verify AFP client is enabledCheck if the AFP client daemon is loaded or running: run 'launchctl list | grep -i afp' or check for 'afpd' process with 'ps aux | grep -i afp'Affected if AFP client service is currently loaded or running on the system
-
Inspect for AFP mount activityCheck for AFP-mounted shares by running 'ls /Volumes' and look for network volumes, or run 'mount' to list all mounted filesystems and look for 'afp://' entriesAffected if There are currently mounted AFP shares or recent AFP connection activity
System is vulnerable if macOS version falls below 14.7.6 or is in the 15.0-15.4.x range AND the AFP client feature is enabled or has been used to connect to AFP servers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped14.7.615.5
Apply macOS Sequoia 15.5 or macOS Sonoma 14.7.6 security update. Avoid connecting to untrusted AFP servers until patched.
macOS Sequoia 15.5 or macOS Sonoma 14.7.6 (depending on which major version is currently installed)
- Check the current macOS version by clicking the Apple menu and selecting 'About This Mac'
- If running macOS 15.0 through 15.4 (Sequoia), upgrade to macOS 15.5 by going to System Settings > General > Software Update
- If running macOS 14.0 through 14.7.5 (Sonoma), upgrade to macOS 14.7.6 by going to System Settings > General > Software Update
- Ensure the upgrade completes successfully and restart the system when prompted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-31246 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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