CVE-2025-24127
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 checks. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.4, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, tvOS 18.3, visionOS 2.3. Parsing a file may lead to an unexpected app 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 confidenceThis is a file parsing vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS) where parsing a specially crafted file leads to unexpected app termination (denial of service). The fix involved implementing improved input validation checks during file parsing to prevent the crash condition.
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< 17.7.4>= 18.0, < 18.3< 18.3< 13.7.3>= 14.0, < 14.7.3>= 15.0, < 15.3< 18.3< 2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhoneGo to Settings > General > About and note the version number. Alternatively, run `sw_vers` in Terminal on a Mac connected to the device, or check via Apple Configurator, MDM, or device management console.Affected if Version is below 18.3 (e.g., 18.2.x, 18.1, 18.0, or any 17.x version before 17.7.4)
-
Check iPadOS version on iPadGo to Settings > General > About and note the version number. Alternatively, check via Apple Configurator, MDM, or device management console.Affected if Version is 18.2.x, 18.1, 18.0, or below 17.7.4 (e.g., 17.7.3, 17.7.2, etc.)
-
Check macOS versionClick Apple menu > About This Mac, or run `sw_vers` in Terminal. Note the version and build number.Affected if Version is below 13.7.3 (Ventura), between 14.0 and 14.7.2 (Sonoma), or between 15.0 and 15.2.x (Sequoia)
-
Check tvOS versionGo to Settings > General > About > Version on Apple TV, or check via MDM or Apple Configurator.Affected if Version is below 18.3 (e.g., 18.2, 18.1, 18.0, or earlier)
-
Check visionOS versionGo to Settings > General > About on Apple Vision Pro, or check via MDM.Affected if Version is below 2.3 (e.g., 2.2, 2.1, 2.0, or earlier)
If the installed OS version falls within any of the affected ranges listed (unpatched iOS/iPadOS < 18.3 or < 17.7.4, macOS < 13.7.3 or 14.x < 14.7.3 or 15.x < 15.3, tvOS < 18.3, visionOS < 2.3), the environment is vulnerable when parsing untrusted files with the affected parsing component.
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 · scoped2.313.7.314.7.3
Apply the vendor security updates: iOS 18.3, iPadOS 18.3/17.7.4, macOS Sequoia 15.3/Sonoma 14.7.3/Ventura 13.7.3, tvOS 18.3, or visionOS 2.3 depending on the affected device. Avoid opening untrusted files from unknown sources until the update is applied.
iOS 18.3 / iPadOS 18.3 / iPadOS 17.7.4 / macOS Sequoia 15.3 / macOS Sonoma 14.7.3 / macOS Ventura 13.7.3 / tvOS 18.3 / visionOS 2.3 (depending on device and initial version)
- Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, or Vision Pro)
- Determine the current installed OS version from Settings > General > About (iOS/iPadOS) or System Settings/About This Mac (macOS)
- For iPhone/iPad: Go to Settings > General > Software Update and install the latest available update (iOS 18.3 or iPadOS 18.3/17.7.4 depending on your device)
- For Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15.3, Sonoma 14.7.3, or Ventura 13.7.3 as applicable
- For Apple TV: Go to Settings > System > Software Updates and update to tvOS 18.3
- For Vision Pro: Go to Settings > General > Software Update and update to visionOS 2.3
- After updating, verify the update was successful by checking Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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-24127 — 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-24127 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