CVE-2026-20641 json
A privacy issue was addressed with improved checks.
published 2026-02-11 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-5934
- cvss
- 7.1
- 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 5%
- public exploits
- 0
- none known
Summary
A privacy issue was addressed with improved checks. This issue is fixed in iOS 18.7.5 and iPadOS 18.7.5, iOS 26.3 and iPadOS 26.3, macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.3, tvOS 26.3, visionOS 26.3, watchOS 26.3. An app may be able to identify what other apps a user has installed.
Patch / fix
- Apple iOS and iPadOS 18.7.5, 26.3
- Apple macOS 14.8.4, 15.7.4, 26.3
- Apple tvOS 26.3
- Apple visionOS 26.3
- Apple watchOS 26.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
support.apple.com
/en-us/126346
release-notes, vendor-advisory
-
support.apple.com
/en-us/126347
release-notes, vendor-advisory
-
support.apple.com
/en-us/126348
release-notes, vendor-advisory
-
support.apple.com
/en-us/126349
release-notes, vendor-advisory
-
support.apple.com
/en-us/126350
release-notes, vendor-advisory
-
support.apple.com
/en-us/126351
release-notes, vendor-advisory
-
support.apple.com
/en-us/126352
release-notes, vendor-advisory
-
support.apple.com
/en-us/126353
release-notes, vendor-advisory
Sources
- CVE List CVE-2026-20641
- NVD CVE-2026-20641
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.