CVE-2025-43379 json
This issue was addressed with improved validation of symlinks.
published last yr. modified 22d ago also EUVD-2025-37711
- 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 11%
- public exploits
- 0
- none known
Summary
This issue was addressed with improved validation of symlinks. This issue is fixed in iOS 26.1 and iPadOS 26.1, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1. An app may be able to access protected user data.
Patch / fix
- Apple iOS and iPadOS 26.1
- Apple macOS 14.8.2, 15.7.2, 26.1
- Apple tvOS 26.1
- Apple visionOS 26.1
- Apple watchOS 26.1
Is CVE-2025-43379 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
- last yr.
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
support.apple.com
/en-us/125632
release-notes, vendor-advisory
-
support.apple.com
/en-us/125635
release-notes, vendor-advisory
-
support.apple.com
/en-us/125636
release-notes, vendor-advisory
-
support.apple.com
/en-us/125637
release-notes, vendor-advisory
-
support.apple.com
/en-us/125638
release-notes, vendor-advisory
-
support.apple.com
/en-us/125639
release-notes, vendor-advisory
- support.apple.com /en-us/125634
Sources
- CVE List CVE-2025-43379
- NVD CVE-2025-43379
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.