dbcve.org
macOSOperating system · Apple

CVE-2025-24130

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 13.7.3 / 14.7.3 or later.
See remediation →
58/100
Remediation priority · Elevated
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 checks. This issue is fixed in macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3. An app may be able to modify protected parts of the file system.

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 · low confidence

This is a macOS authorization vulnerability where an application could potentially bypass file system restrictions and modify protected parts of the file system. The issue was addressed with improved authorization checks in the affected macOS versions.

MitigationApply the macOS security updates (Sequoia 15.3, Sonoma 14.7.3, or Ventura 13.7.3) to all affected systems. For enterprise environments, deploy via MDM or 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
macOSOperating system
Affected:< 13.7.3>= 14.0, < 14.7.3>= 15.0, < 15.3

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 macOS version via sw_vers
    Run 'sw_vers -productVersion' in Terminal to get the installed macOS version (e.g., 14.6, 15.2, etc.)
    Affected if The version falls within any of these vulnerable ranges: Ventura < 13.7.3, Sonoma < 14.7.3, or Sequoia < 15.3
  2. Confirm macOS release name
    Run 'sw_vers -productName' to determine if the system is Ventura, Sonoma, or Sequoia, then cross-reference with the version from step 1
    Affected if The combination of release name and version number matches the vulnerable ranges listed above
  3. Alternative detailed version check
    Run 'system_profiler SPSoftwareDataType' to see detailed system software information including the exact OS build version
    Affected if The OS build version is earlier than the fixed builds for your macOS release (13.7.3, 14.7.3, or 15.3 respective security updates)
  4. Verify security update status
    Check System Settings > General > Software Update to see if the relevant security update (associated with CVE-2025-24130) has been installed
    Affected if The security update is not present or the system shows no available updates despite being in a vulnerable version range

A system is affected if it runs macOS Ventura earlier than 13.7.3, macOS Sonoma earlier than 14.7.3, or macOS Sequoia earlier than 15.3, as these versions lack the improved authorization checks that fix the file system restriction bypass vulnerability.

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.3 / 14.7.3 / 15.3 or later
Fixed in 13.7.314.7.315.3
Interim mitigation

Apply the macOS security updates (Sequoia 15.3, Sonoma 14.7.3, or Ventura 13.7.3) to all affected systems. For enterprise environments, deploy via MDM or standard patch management processes.

Recommended fix High confidence

macOS Ventura 13.7.3, macOS Sonoma 14.7.3, or macOS Sequoia 15.3 (depending on your current major version)

  1. 1. Back up important data using Time Machine or another backup solution
  2. 2. Connect your Mac to a power source to prevent interruption during the update
  3. 3. Open System Settings (or System Preferences on older macOS versions)
  4. 4. Click on General in the sidebar
  5. 5. Click Software Update
  6. 6. Wait for macOS to check for available updates
  7. 7. If an update to the fixed version is available (Ventura 13.7.3, Sonoma 14.7.3, or Sequoia 15.3), click Download and Install
  8. 8. Follow the on-screen instructions and allow the Mac to restart to complete the installation
Caveat Standard macOS upgrade risks apply - ensure full backup before proceeding; some legacy applications may not be compatible with newer macOS versions

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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