Apple Xcode 27.2 Fixes File and Sensitive-Data Access
Tech GuruQuick Answer
Apple released Xcode 27.2 for macOS Tahoe 26.6 and later with fixes for CVE-2026-112602 and CVE-2026-112605. Inventory developer and CI systems, update through Apple's supported channel, validate signing and build workflows, review sensitive-data access where warranted, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory developer Macs and build hosts with Xcode, exact versions, CoreDevice and Instruments use, signing identities, CI runners, owners, and maintenance windows. Match systems to Apple's Xcode and macOS availability statement; do not infer applicability to unrelated Apple products or treat application presence as evidence of data access. Install Xcode 27.2 through Apple's supported distribution channel and update managed build images and CI runners that carry older Xcode releases. Confirm the selected Xcode path and version, test builds, signing, device workflows and Instruments, review relevant access evidence where warranted, and retain package and change records.
Last verified: 2026-10-30 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Apple Xcode on macOS Tahoe 26.6 and later |
|---|---|
| Advisory | Apple Xcode 27.2 |
| CVEs | CVE-2026-112602, CVE-2026-112605 |
| Authoritative release date | 2026-10-29 |
| Authority revision date | 2026-10-30 |
| Affected versions | Xcode releases before 27.2 on macOS Tahoe 26.6 and later for the CoreDevice symlink and Instruments authorization issues described by Apple. |
| Fixed version | Xcode 27.2 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Apple does not state that these vulnerabilities are being maliciously exploited.; no exploitation claim is inferred. |
What Changed
Apple fixed a CoreDevice symlink-handling issue that could expose arbitrary files and an Instruments authorization issue that could expose sensitive user data.
What To Validate Now
- Inventory. Inventory developer Macs and build hosts with Xcode, exact versions, CoreDevice and Instruments use, signing identities, CI runners, owners, and maintenance windows.
- Establish applicability. Match systems to Apple's Xcode and macOS availability statement; do not infer applicability to unrelated Apple products or treat application presence as evidence of data access.
- Remediate. Install Xcode 27.2 through Apple's supported distribution channel and update managed build images and CI runners that carry older Xcode releases.
- Validate. Confirm the selected Xcode path and version, test builds, signing, device workflows and Instruments, review relevant access evidence where warranted, and retain package and change records.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Xcode updates can change SDKs, simulators and build output. Protect signing material, stage critical pipelines, and do not copy sensitive artifacts into ordinary tickets.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
