CVE-2026-39877: Buffer Overflow
A memory corruption issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8. An app may be able to disclose kernel memory.
Other sources
Accounts. A parsing issue in the handling of directory paths was addressed with improved path validation.
— Apple
afpfs. A buffer overflow was addressed with improved bounds checking.
— Apple
apache. This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.
— Apple
APFS. The issue was addressed with improved memory handling.
— Apple
App Store. This issue was addressed with improved checks.
— Apple
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.7.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 14.8.8 - Upgrade
Upgrade
macOS Sequoiato a version that resolves this vulnerability.Fixed in 15.7.8 - Upgrade
Upgrade
macOS Sonomato a version that resolves this vulnerability.Fixed in 14.8.8
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-43749
- CVE-2026-64767
- CVE-2026-23918
- CVE-2026-64695
- CVE-2026-43801
- CVE-2026-43781
- CVE-2026-64737
- CVE-2026-43748
- CVE-2026-43776
- CVE-2026-43681
- CVE-2026-43672
- CVE-2026-43763
- CVE-2026-64702
- CVE-2026-64725
- CVE-2026-64747
- CVE-2026-64762
- CVE-2026-64707
- CVE-2026-28849
- CVE-2026-64698
- CVE-2026-64734
- CVE-2026-43756
- CVE-2026-43693
- CVE-2026-43673
- CVE-2026-43744
- CVE-2026-43803
- CVE-2026-43775
- CVE-2026-43711
- CVE-2026-28936
- CVE-2026-43738
- CVE-2026-43802
- CVE-2026-64710
- CVE-2026-39875
- CVE-2026-43698
- CVE-2026-3784
- CVE-2026-3783
- CVE-2026-43758
- CVE-2026-64708
- CVE-2026-28926
- CVE-2026-43747
- CVE-2026-64694
- CVE-2026-28945
- CVE-2026-64776
- CVE-2026-43793
- CVE-2026-43753
- CVE-2026-43714
- CVE-2026-64740
- CVE-2026-43796
- CVE-2026-64692
- CVE-2026-43682
- CVE-2026-28981
- CVE-2026-43773
- CVE-2026-43767
- CVE-2026-64697
- CVE-2026-43764
- CVE-2026-43710
- CVE-2025-43325
- CVE-2026-64716
- CVE-2026-43780
- CVE-2026-43818
- CVE-2026-43661
- CVE-2026-64754
- CVE-2026-64693
- CVE-2026-43805
- CVE-2026-39877
- CVE-2026-64749
- CVE-2026-43782
- CVE-2026-64744
- CVE-2026-64775
- CVE-2026-28982
- CVE-2026-43778
- CVE-2026-64735
- CVE-2026-43822
- CVE-2026-64700
- CVE-2026-43799
- CVE-2026-43810
- CVE-2026-43724
- CVE-2026-43722
- CVE-2026-43809
- CVE-2026-43757
- CVE-2026-43769
- CVE-2026-43754
- CVE-2026-64723
- CVE-2026-39868
- CVE-2026-64709
- CVE-2026-64721
- CVE-2026-20672
- CVE-2026-28983
- CVE-2026-4424
- CVE-2026-28900
- CVE-2026-28973
- CVE-2026-64739
- CVE-2026-43703
- CVE-2026-43706
- CVE-2026-43766
- CVE-2026-64738
- CVE-2026-43653
- CVE-2026-64724
- CVE-2026-43723
- CVE-2026-43807
- CVE-2026-43733
- CVE-2026-43729
- CVE-2026-64772
- CVE-2026-64774
- CVE-2026-64770
- CVE-2026-64769
- CVE-2026-64722
- CVE-2026-64768
- CVE-2026-64771
- CVE-2026-43771
- CVE-2026-43772
- CVE-2026-28961
- CVE-2026-64711
- CVE-2026-28912
- CVE-2026-43765
- CVE-2026-28896
- CVE-2026-64731
- CVE-2026-43812
- CVE-2026-43694
- CVE-2026-39874
- CVE-2026-64764
- CVE-2026-64763
- CVE-2026-64766
- CVE-2026-64765
- CVE-2026-43779
- CVE-2026-43777
- CVE-2026-43665
- CVE-2026-64745
- CVE-2026-39873
- CVE-2026-64696
- CVE-2026-64704
- CVE-2026-43774
- CVE-2026-43770
- CVE-2026-43768
- CVE-2026-64703
- CVE-2026-64699
- CVE-2026-43750
- CVE-2026-28932
- CVE-2026-28914
- CVE-2026-28911
- CVE-2026-43760
- CVE-2026-43755
Frequently Asked Questions
What is the severity of CVE-2026-39877?
The severity of CVE-2026-39877 is rated high with a CVSS score of 7.8.
How do I fix CVE-2026-39877?
CVE-2026-39877 can be fixed by updating to macOS Sequoia 15.7.8 or macOS Sonoma 14.8.8.
What type of vulnerability is CVE-2026-39877?
CVE-2026-39877 is a memory corruption vulnerability that involves issues such as buffer overflow and input validation.
What potential risks does CVE-2026-39877 pose?
CVE-2026-39877 may allow an application to disclose kernel memory, which can compromise system security.
When was CVE-2026-39877 published?
CVE-2026-39877 was published on July 27, 2026.