CVE-2025-31203
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 · uneditedAn integer overflow was addressed with improved input validation. 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, tvOS 18.4, visionOS 2.4, watchOS 11.4. An attacker on the local network 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 confidenceThis is a denial-of-service vulnerability in Apple operating systems caused by an integer overflow that was addressed through improved input validation. An attacker on the local network can trigger the overflow, potentially causing the affected device to become unresponsive or crash.
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< 14.7.5>= 15.0, < 15.4< 18.4< 2.4< 11.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/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 iPhoneOpen Settings > General > About and note the version number, or run 'sw_vers' in Terminal if the device is jailbroken/has remote access toolsAffected if Version is below 18.4 (or below 17.7.6 if on iOS 17.x branch)
-
Check iPadOS version on iPadOpen Settings > General > About and note the version numberAffected if Version is below 17.7.6, or >= 18.0 but below 18.4
-
Check macOS version on MacOpen System Settings > General > About, or run 'sw_vers' in Terminal, or run 'system_profiler SPSoftwareDataType'Affected if Version is below 14.7.5 (Sonoma), or >= 15.0 but below 15.4 (Sequoia)
-
Check tvOS version on Apple TVOpen Settings > General > About > Version on the Apple TV deviceAffected if Version is below 18.4
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone > My Watch > General > About, or check Settings > General > About on the WatchAffected if Version is below 11.4
-
Check visionOS version on Vision ProOpen Settings > General > About on the Vision Pro deviceAffected if Version is below 2.4
If the detected OS version falls within any of the affected ranges listed above and the device is connected to a network where untrusted local attackers may be present, the device is likely vulnerable to this denial-of-service flaw.
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.411.414.7.5
Apply the available vendor patches by updating affected devices to iOS 18.4/iPadOS 18.4/17.7.6, macOS Sequoia 15.4/Sonoma 14.7.5, tvOS 18.4, visionOS 2.4, or watchOS 11.4 as appropriate for each device.
iOS 18.4 / iPadOS 17.7.6, iPadOS 18.4 / macOS Sonoma 14.7.5, macOS Sequoia 15.4 / tvOS 18.4 / visionOS 2.4 / watchOS 11.4 (depending on device)
- Identify the current version of the affected Apple operating system on the device
- For iPadOS 17.x devices: upgrade to iPadOS 17.7.6
- For iPadOS 18.x devices: upgrade to iPadOS 18.4
- For iPhone/iOS devices: upgrade to iOS 18.4
- For macOS Sonoma (14.x) devices: upgrade to macOS Sonoma 14.7.5
- For macOS Sequoia (15.x) devices: upgrade to macOS Sequoia 15.4
- For tvOS devices: upgrade to tvOS 18.4
- For visionOS devices: upgrade to visionOS 2.4
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-31203 — 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-31203 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