Quick answers
- Is CVE-2026-86874 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86874 being exploited in the wild.
- How severe is CVE-2026-86874?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Apple Xcode before 27.
- Is there a fix for CVE-2026-86874?
- Yes: fixed in Xcode 27. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86874 attacked?
- It is attacked with local access, in a web application.
- Am I affected by CVE-2026-86874?
- Check whether you run Apple Xcode 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: Xcode 27
Technical details
The otool binary parser contains an out-of-bounds read vulnerability triggered when processing a maliciously crafted binary file. The flaw stems from insufficient input validation and allows an attacker with a specially crafted binary to cause unexpected tool termination. The vulnerability is fixed in Xcode 27 via improved input validation in the parsing logic.
Affected products
- Apple Xcode before 27
Timeline
- 2026-10-19: disclosed
- 2026-09-14: patched: Xcode 27 released