Mac bugs and fixes September 17 2026: macOS 27

What broke in macOS 27?

Blakecrosley said on September 16, 2026 that macOS 27 changed Rosetta behavior without identifying a corrective point release.

According to Blakecrosley on September 16, 2026, an application previously configured with Open using Rosetta launches natively, potentially leaving an Intel plug-in unloaded when the application first opens after the upgrade. Blakecrosley described reapplying the setting as a reading of Apple’s instructions rather than a tested result, because a Mac running macOS 27 was unavailable for that test.

Blakecrosley also said on September 16, 2026 that previously installed Rosetta is not restored automatically during the upgrade, while Intel-based plug-ins and loaders may disappear from Settings or fail to produce incompatibility notifications. Installer packages without hostArchitecture now default to arm64, so Blakecrosley said on September 16, 2026 that package scripts must behave correctly under arm64.

I regard the missing warning as the practical problem because a native launch can look successful while an expected Intel component remains absent, based on Blakecrosley’s September 16, 2026 account. Apple’s exact boundary, as relayed by Blakecrosley on September 16, 2026, keeps Rosetta available on any Mac with Apple silicon using macOS 27 or earlier.

Has a macOS update fix shipped?

No macOS update fix for the Rosetta changes had shipped in the sources dated through September 16, 2026, according to Blakecrosley.

Apple Support’s September 14, 2026 security-content document identifies macOS Golden Gate 27 as the released version, but the document does not identify a later point release that reverses the Rosetta launch or restoration behavior. Blakecrosley’s September 16, 2026 account likewise describes those changes as macOS 27 behavior rather than defects corrected by another build.

I separate that unresolved compatibility problem from the fixes already included in macOS Golden Gate 27, because Apple Support said on September 14, 2026 that the release corrected security defects. A security release can contain important repairs without correcting behavior introduced by the same major upgrade, and the dated Apple Support and Blakecrosley documents describe exactly that split.

My Mac bugs and fixes for September 16, 2026 provides the preceding release-day context. For September 17, 2026, the honest status is unchanged: no cited source names a shipped Rosetta correction, so I will not invent a version or promise a point release.

Which Mac known issues have credible reports?

SANS Stormcast on September 14, 2026 described a possible Safari single sign-on problem after macOS 27.

Johannes Olri said in SANS Stormcast on September 14, 2026 that Safari had trouble with a Microsoft single sign-on handover at one particular site, while other browsers did not show the problem after the upgrade. The same SANS Stormcast account said on September 14, 2026 that Safari was updated with the release and that no other specific problems had been seen.

I treat that account as a limited observation rather than a broad Apple acknowledgment because SANS Stormcast tied it to one site on September 14, 2026. No cited Apple document names the single sign-on behavior, its cause or a shipped fix, so its wider scope remains unknown.

The September 14, 2026 installation guide describes another visible symptom: a Mac remaining at the Apple logo or progress bar while installing macOS 27. The guide advises keeping the Mac connected to power while progress continues, then using a forced restart or Safe Mode only after progress has stopped for a long time.

Those macOS bugs do not have equal evidence: SANS Stormcast’s September 14, 2026 browser observation is narrow, while the installation guide dated September 14, 2026 supplies recovery steps but no Apple diagnosis.

What security fixes shipped with macOS Golden Gate 27?

Apple shipped security fixes in macOS Golden Gate 27 on September 14, 2026, according to Apple Support.

Apple Support said on September 14, 2026 that CVE-2026-86882 involved an out-of-bounds write in Accelerate Framework, where processing a maliciously crafted image could terminate a process unexpectedly. Apple Support also said on September 14, 2026 that improved bounds checking addressed the defect.

For CVE-2026-43664, Apple Support said on September 14, 2026 that an application could access sensitive user data through an Accessibility issue, which improved data protection corrected. The same Apple Support document dated September 14, 2026 says an Accounts authorization issue could let a malicious application bypass Privacy preferences, with improved state management providing the correction.

Published totals differ. iTnews said on September 15, 2026 that macOS 27 fixes over 200 vulnerabilities, while AskWoody said on September 15, 2026 that the release fixes over 100 vulnerabilities. SANS Stormcast gave 261 vulnerabilities on September 14, 2026, but the cited Apple Support extract does not supply a total that resolves the difference.

I therefore treat the individual Apple entries as authoritative and avoid presenting a disputed total as settled. The Apple security update matters, but Apple Support’s September 14, 2026 security document does not claim to repair the Rosetta compatibility changes.

What can a Mac user do today?

Update Little Snitch before macOS 27, SANS Stormcast advised on September 14, 2026; otherwise delay the major upgrade when compatibility matters.

SANS Stormcast said on September 14, 2026 that Little Snitch had received an update intended for installation before macOS 27, while BlockBlock had received a release improving macOS 27 compatibility. The same source said a separate OS 26.7 release contains bug and security fixes without new features, making it an available choice for someone who wants to postpone the major upgrade.

Delaying macOS 27 costs access to its new features and its included security fixes, according to SANS Stormcast on September 14, 2026 and Apple Support on September 14, 2026. Proceeding instead costs time for compatibility checks, particularly when work depends on Rosetta, Intel plug-ins, loaders or installer scripts affected by the behavior Blakecrosley documented on September 16, 2026.

If the macOS 27 installer is still moving, the September 14, 2026 installation guide says to keep the Mac connected to power and avoid turning it off. If progress has stopped for a long time, the same guide recommends holding the power button until shutdown, restarting, and checking whether installation resumes.

If a restart does not help, the September 14, 2026 guide recommends shutting down, holding the power button until startup options appear, selecting the startup disk, holding Shift and choosing Safe Mode. I would not treat those recovery steps as a shipped Apple fix, because the guide dated September 14, 2026 does not identify an Apple acknowledgment, root cause or corrective release.