dbcve.org
macOSOperating system · Apple

CVE-2025-24199

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 13.7.5 / 14.7.5 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
An uncontrolled format string issue was addressed with improved input validation. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An app may be able to cause a denial-of-service.

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 an uncontrolled format string vulnerability in macOS where user-supplied input was not properly validated before being used in format string functions. An attacker with the ability to supply specially crafted input could crash the affected application (denial-of-service) by causing the application to read from or write to invalid memory addresses via format string specifiers.

MitigationUpdate macOS to version 15.4 (Sequoia), 14.7.5 (Sonoma), or 13.7.5 (Ventura) or later, which contain the fix with improved input validation for format string handling.

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.0, < 13.7.5>= 14.0, < 14.7.5>= 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 your macOS version via System Settings
    Open System Settings (or System Preferences on older macOS), go to General > About, and note the version number displayed next to 'macOS'
    Affected if The version shown is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3.x (anything less than 13.7.5, 14.7.5, or 15.4)
  2. Check your macOS version via Terminal
    Open Terminal and run 'sw_vers -productVersion' to display the exact macOS version number
    Affected if The output shows a version less than 13.7.5, 14.7.5, or 15.4 (for example, 14.7, 15.2, or 13.6.5)
  3. Confirm the major version number
    Run 'uname -r' in Terminal to see the kernel release, or check the macOS release name (Ventura = 13.x, Sonoma = 14.x, Sequoia = 15.x)
    Affected if The system is running Ventura (13.x), Sonoma (14.x), or Sequoia (15.0-15.3) and the specific point release is below the fixed versions

You are affected if your macOS version is 13.0 through 13.7.4, 14.0 through 14.7.4, or 15.0 through 15.3 - the vulnerability is present in the OS itself and applies to any application using format string functions with unsanitized input.

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.5 / 14.7.5 / 15.4 or later
Fixed in 13.7.514.7.515.4
Interim mitigation

Update macOS to version 15.4 (Sequoia), 14.7.5 (Sonoma), or 13.7.5 (Ventura) or later, which contain the fix with improved input validation for format string handling.

Recommended fix High confidence

macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4 (depending on your current major version)

  1. Back up your Mac using Time Machine or another backup method before applying any system updates
  2. Verify your current macOS version by clicking the Apple menu > About This Mac
  3. For macOS Ventura (13.x) users: Update to macOS Ventura 13.7.5 by going to System Settings > General > Software Update and installing the available update
  4. For macOS Sonoma (14.x) users: Update to macOS Sonoma 14.7.5 by going to System Settings > General > Software Update and installing the available update
  5. For macOS Sequoia (15.x) users: Update to macOS Sequoia 15.4 by going to System Settings > General > Software Update and installing the available update
  6. After updating, verify the update was successful by checking About This Mac to confirm the version number matches the fixed release
Caveat Standard macOS update risks apply - ensure important data is backed up before updating; some legacy software 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
  • 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-24199 — 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-24199 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