CVE-2026-112567 json
This issue was addressed with improved checks.
published 14d ago modified 4d ago also EUVD-2026-110353
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
This issue was addressed with improved checks. This issue is fixed in iOS 27.2 and iPadOS 27.2, macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2, tvOS 27.2, visionOS 27.2, watchOS 27.2. A malicious application may be able to bypass Privacy preferences.
Patch / fix
- Apple iOS and iPadOS 27.2
- Apple macOS 15.8.2, 26.7.2, 27.2
- Apple tvOS 27.2
- Apple visionOS 27.2
- Apple watchOS 27.2
Is CVE-2026-112567 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
- yes
- Technical impact
- partial
- Assessed
- 6d ago
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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-284 Improper Access Control
References
-
support.apple.com
/en-us/149230
vendor-advisory, release-notes
-
support.apple.com
/en-us/149521
vendor-advisory, release-notes
-
support.apple.com
/en-us/149522
vendor-advisory, release-notes
-
support.apple.com
/en-us/149523
vendor-advisory, release-notes
-
support.apple.com
/en-us/149524
vendor-advisory, release-notes
-
support.apple.com
/en-us/149525
vendor-advisory, release-notes
-
support.apple.com
/en-us/149526
vendor-advisory, release-notes
Sources
- CVE List CVE-2026-112567
- NVD CVE-2026-112567
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.