Remote memory disclosure via integer overflow
Published May 12, 2025 · Updated Apr 2, 2026
An integer overflow in the Security component of Apple operating systems allows remote attackers to leak memory over a network. Apple identifies the locus only as the Security component and states that insufficient input validation permits the integer overflow. No authentication or user interaction is required; the documented consequence is memory disclosure, and Apple has not published the affected protocol or data path.
Summary
What happened
An integer overflow in the Security component of Apple operating systems allows remote attackers to leak memory over a network. Apple identifies the locus only as the Security component and states that insufficient input validation permits the integer overflow. No authentication or user interaction is required; the documented consequence is memory disclosure, and Apple has not published the affected protocol or data path.
The record
- CVE
- CVE-2025-31221
- Published
- May 12, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2025CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <18.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo