CVE-2025-43532 json
A memory corruption issue was addressed with improved bounds checking.
published 10mo ago modified last mo. also EUVD-2025-203155
- cvss
- 2.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
A memory corruption issue was addressed with improved bounds checking. This issue is fixed in iOS 18.7.3 and iPadOS 18.7.3, iOS 26.2 and iPadOS 26.2, macOS Sequoia 15.7.3, macOS Sonoma 14.8.3, macOS Tahoe 26.2, tvOS 26.2, visionOS 26.2, watchOS 26.2. Processing malicious data may lead to unexpected app termination.
Patch / fix
- Apple iOS and iPadOS 18.7.3, 26.2
- Apple macOS 14.8.3, 15.7.3, 26.2
- Apple tvOS 26.2
- Apple visionOS 26.2
- Apple watchOS 26.2
Is CVE-2025-43532 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 2.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |
| CNA | 3.1 | 2.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
support.apple.com
/en-us/125887
release-notes, vendor-advisory
-
support.apple.com
/en-us/125888
release-notes, vendor-advisory
- support.apple.com /en-us/125884
- support.apple.com /en-us/125885
- support.apple.com /en-us/125886
- support.apple.com /en-us/125889
- support.apple.com /en-us/125890
- support.apple.com /en-us/125891
Sources
- CVE List CVE-2025-43532
- NVD CVE-2025-43532
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.