Quick answers
- Is CVE-2026-113950 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113950 being exploited in the wild.
- How severe is CVE-2026-113950?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Apple Ios before 27.2; Apple iPadOS before 27.2; Apple macOS Golden Gate before 27.2; Apple Tvos before 27.2; and 2 more.
- Is there a fix for CVE-2026-113950?
- Yes: fixed in iOS 27.2, iPadOS 27.2, macOS Golden Gate 27.2, tvOS 27.2, visionOS 27.2, watchOS 27.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113950 attacked?
- It is attacked over the network or from the adjacent network or with local access, in an operating system.
- Am I affected by CVE-2026-113950?
- Check whether you run Apple Ios, Apple iPadOS, Apple macOS Golden Gate or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: iOS 27.2, iPadOS 27.2, macOS Golden Gate 27.2, tvOS 27.2, visionOS 27.2, watchOS 27.2
Technical details
An out-of-bounds write issue in font parsing was fixed with improved bounds checking across Apple's operating systems. The vulnerability is triggered by processing a maliciously crafted font file and can result in unexpected app termination or process memory corruption. No authentication or user interaction is required beyond opening a malicious font, making this exploitable through various delivery vectors.
Affected products
- Apple iOS before 27.2
- Apple iPadOS before 27.2
- Apple macOS Golden Gate before 27.2
- Apple tvOS before 27.2
- Apple visionOS before 27.2
- Apple watchOS before 27.2
Timeline
- 2026-10-26: disclosed