CVE-2025-24190
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 iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, watchOS 11.4. Processing a maliciously crafted video file may lead to unexpected app termination or corrupt process 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 confidenceMemory handling vulnerability in video processing components across multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allows processing of maliciously crafted video files to cause memory corruption, leading to unexpected app termination or process memory corruption.
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.6>= 18.0, < 18.4< 18.4>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4< 18.4all versions< 2.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 iOS version on iPhoneGo to Settings > General > About > Version. Alternatively, connect to a computer and run: idevicesyslog 2>/dev/null | grep -i 'os version' or check via Apple Configurator or Finder.Affected if Version is lower than 18.4 (e.g., 17.x or 18.0-18.3)
-
Check iPadOS version on iPadGo to Settings > General > About > Version. Alternatively, connect to a computer and use: iprofiler or check via Apple Configurator or Finder.Affected if Version is lower than 17.7.6 OR between 18.0 and 18.3 (inclusive)
-
Check macOS versionClick Apple menu > About This Mac. The version number appears below the marketing name. For command line, run: sw_vers -productVersionAffected if Version is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3.x
-
Check tvOS versionGo to Settings > General > About > Version. Alternatively, use Xcode or a network scanner to query the Apple TV device info.Affected if Version is lower than 18.4 (any version below 18.4 is affected)
-
Check visionOS versionGo to Settings > About > Version. This applies to Apple Vision Pro devices.Affected if Version is lower than 2.4
A device is affected if it runs any unpatched version of iOS, iPadOS, macOS, tvOS, or visionOS within the ranges listed above, particularly when processing untrusted video files.
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.413.7.514.7.5
Apply vendor-supplied security updates: iOS 18.4, iPadOS 18.4/17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, or watchOS 11.4 as appropriate for each affected system.
iOS 18.4/iPadOS 18.4/iPadOS 17.7.6, macOS Ventura 13.7.5, macOS Sonoma 14.7.5, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4
- For iPadOS: Upgrade to iPadOS 17.7.6 or iPadOS 18.4 (depending on your device's supported iOS version)
- For iPhone: Upgrade to iOS 18.4
- For macOS Ventura (13.x): Upgrade to macOS Ventura 13.7.5
- For macOS Sonoma (14.x): Upgrade to macOS Sonoma 14.7.5
- For macOS Sequoia (15.x): Upgrade to macOS Sequoia 15.4
- For tvOS: Upgrade to tvOS 18.4
- For visionOS: Upgrade to visionOS 2.4
- After upgrading, verify the system reports the correct version in Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24190 — 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-24190 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