Memory corruption via undisclosed libnetcore file handling
Published Apr 2, 2026 · Updated Apr 2, 2026
Memory corruption in Apple libnetcore before iOS and iPadOS 18.6 and macOS 15.6 allows remote attackers to corrupt memory via a file. Apple states only that improved memory handling addressed the issue and has not disclosed the libnetcore parsing routine or the erroneous operation performed on file data. Exploitation requires user interaction to process the file; Apple has not published a more specific consequence than memory corruption.
Summary
What happened
Memory corruption in Apple libnetcore before iOS and iPadOS 18.6 and macOS 15.6 allows remote attackers to corrupt memory via a file. Apple states only that improved memory handling addressed the issue and has not disclosed the libnetcore parsing routine or the erroneous operation performed on file data. Exploitation requires user interaction to process the file; Apple has not published a more specific consequence than memory corruption.
The record
- CVE
- CVE-2025-43202
- Published
- Apr 2, 2026
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2026CVE 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.6
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.
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