CVE-2025-43346 json
An out-of-bounds access issue was addressed with improved bounds checking.
published 2025-09-15 13 mo ago modified 2026-11-03 5 d ago also EUVD-2025-29345
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
An out-of-bounds access issue was addressed with improved bounds checking. This issue is fixed in iOS 18.7 and iPadOS 18.7, iOS 26 and iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. Processing a maliciously crafted media file may lead to unexpected app termination or corrupt process memory.
Patch / fix
- Apple iOS and iPadOS 18.7, 26
- Apple macOS 26
- Apple tvOS 26
- Apple visionOS 26
- Apple watchOS 26
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 13 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
support.apple.com
/en-us/125108
release-notes, vendor-advisory
-
support.apple.com
/en-us/125109
release-notes, vendor-advisory
-
support.apple.com
/en-us/125114
release-notes, vendor-advisory
-
support.apple.com
/en-us/125115
release-notes, vendor-advisory
-
support.apple.com
/en-us/125116
release-notes, vendor-advisory
- support.apple.com /en-us/125110
- seclists.org /fulldisclosure/2025/Sep/57
- seclists.org /fulldisclosure/2025/Sep/56
- seclists.org /fulldisclosure/2025/Sep/53
- seclists.org /fulldisclosure/2025/Sep/58
- seclists.org /fulldisclosure/2025/Sep/49
Sources
- CVE List CVE-2025-43346
- NVD CVE-2025-43346
Fencer Vulns 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.