CVE-2025-43277 json
The issue was addressed with improved memory handling.
published 2025-07-29 15 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-23052
- cvss
- 7.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 23%
- public exploits
- 0
- none known
Summary
The issue was addressed with improved memory handling. This issue is fixed in iOS 18.6 and iPadOS 18.6, macOS Sequoia 15.6, macOS Sonoma 14.8, tvOS 18.6, visionOS 2.6, watchOS 11.6. Processing a maliciously crafted audio file may lead to memory corruption.
Patch / fix
- Apple iOS and iPadOS 18.6
- Apple macOS 14.8, 15.6
- Apple tvOS 18.6
- Apple visionOS 2.6
- Apple watchOS 11.6
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 15 mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
support.apple.com
/en-us/125112
release-notes, vendor-advisory
- support.apple.com /en-us/124147
- support.apple.com /en-us/124149
- support.apple.com /en-us/124153
- support.apple.com /en-us/124154
- support.apple.com /en-us/124155
- seclists.org /fulldisclosure/2025/Sep/55
- seclists.org /fulldisclosure/2025/Jul/37
- seclists.org /fulldisclosure/2025/Jul/35
- seclists.org /fulldisclosure/2025/Jul/32
- seclists.org /fulldisclosure/2025/Jul/30
Sources
- CVE List CVE-2025-43277
- NVD CVE-2025-43277
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.