Cyber Resilience

CVE-2025-31251

DoS in Apple Macos ≤ 13.7.6

Published
12 May 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0027 19th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-31251 is a medium-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Apple Macos. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

The issue was addressed with improved input sanitization. This issue is fixed in iOS 18.5 and iPadOS 18.5, iPadOS 17.7.7, macOS Sequoia 15.5, macOS Sonoma 14.7.6, macOS Ventura 13.7.6, tvOS 18.5, visionOS 2.5, watchOS 11.5. Processing a maliciously crafted media…

more

file may lead to unexpected app termination or corrupt process memory.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-44176Same product: Apple Ipados
CVE-2025-24126Same product: Apple Ipados
CVE-2024-27800Same product: Apple Ipados
CVE-2025-31226Same product: Apple Ipados
CVE-2026-20650Same product: Apple Ipados
CVE-2024-44169Same product: Apple Ipados
CVE-2024-44183Same product: Apple Ipados
CVE-2024-54658Same product: Apple Ipados
CVE-2025-31245Same product: Apple Ipados
CVE-2025-24211Same product: Apple Ipados

Affected Assets

apple
ipados
≤ 17.7.7 · 18.0 — 18.5
apple
iphone os
≤ 18.5
apple
macos
≤ 13.7.6 · 14.0 — 14.7.6 · 15.0 — 15.5
apple
tvos
≤ 18.5
apple
visionos
≤ 2.5
apple
watchos
≤ 11.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-16 Memory Protection
  • SC-5 Denial-of-service Protection
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation and sanitization of untrusted input such as media files to block malformed data that triggers uncontrolled resource use or memory corruption.

prevent

Enforces memory-protection mechanisms that limit the ability of a malicious media file to corrupt process memory or cause termination.

prevent

Requires controls that protect against resource-exhaustion conditions (CWE-400) resulting from crafted media files.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.IR-04 mostly match
prevents

Explicitly requires monitoring and maintaining resource capacity, directly addressing uncontrolled consumption to preserve availability.

DE.CM-09 partial match
prevents

Continuous monitoring of computing resources can detect resource exhaustion but does not itself enforce allocation limits.

PR.IR-03 partial match
prevents

Resilience mechanisms such as avoiding single points of failure indirectly reduce impact of resource exhaustion.

PR.PS-01 partial match
prevents

Hardened configuration baselines can include resource quotas and limits that constrain consumption.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

prevents

By continuously monitoring utilization, stress-testing peak loads, and maintaining documented plans to scale or throttle resources, the control directly limits an attacker’s ability to drive a system into uncontrolled resource exhaustion.

detects

Pre-agreed severity-based prioritization and resource allocation during incident triage reduce the likelihood that an attacker-induced resource exhaustion will overwhelm the organization before corrective action is taken.

mitigates

Business-continuity plans that include resource-management controls reduce the likelihood that an attacker can trigger uncontrolled resource consumption by forcing the system into a degraded or fallback state.

mitigates

Defining RTOs and capacity requirements for ICT services during business-impact analysis forces organizations to provision sufficient resources and throttling mechanisms, reducing the likelihood that an attacker can induce denial-of-service through uncontrolled resource consumption.

detects

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

References