Mac bugs and fixes October 28 2026: what shipped

What broke on macOS 27 Golden Gate?

OS X Daily reports sustained dasd CPU use on macOS 27 Golden Gate, and OS X Daily documents a PowerLog database workaround. Its account describes the process hovering between 90-100% CPU usage for several days, with significant battery drain and misplaced processor use. A normal reboot did not stop it. Safe Mode did not stop it either.

The report presents telemetry and the PowerLog background-processing database as a possible connection, not a confirmed diagnosis from Apple. Backing up and erasing that database brought dasd down to 0% CPU after a restart in the reported case. The article advises checking CPU usage after the reboot settles and again after about 10 minutes.

I do not have an Apple acknowledgment or a delivered operating-system correction for the dasd behaviour. The available workaround uses Terminal to remove a system file that is actively being written. That is a meaningful cost. It requires a current backup, careful command entry and acceptance that the operation can go wrong. I would treat it as a last resort rather than routine maintenance.

Has Apple shipped fixes?

Yes. Apple has shipped macOS 27.2 with a large set of security corrections. SecurityWeek says macOS 27.2 fixes 263 flaws.

The SecurityWeek account says the release addresses memory corruption in WebKit, the kernel and components handling images, fonts, PDFs, audio and video files. Some defects could permit arbitrary code execution. The same account describes privacy-preference bypasses, sandbox escapes, Gatekeeper bypasses and kernel memory corruption.

SecurityWeek also attributes fixes to Screen Sharing, Remote Management and SMB. Its report says some affected paths could be targeted remotely or from the local network. A Remote Management defect could allow a remote attacker to execute arbitrary code. This Apple security update therefore answers the shipped-fix part of the status, but it does not establish that the separate dasd problem is corrected.

My practical reading is simple. macOS 27.2 is the named release carrying the documented security fixes. I would install it after checking essential applications and making a backup. I would not describe it as the dasd fix without a dated source making that connection.

Which Mac problem still waits for an update?

A documented gap affects some macOS command-line tools that can still accept compromised eMudhra certificates. MacRumors says Apple has not yet shipped the additional macOS fix.

According to the MacRumors account, Apple has blocked the affected TLS web certificates since October 19 in Safari, Mail and applications using Apple networking and security frameworks. That block is automatic and requires no software update for most device owners. MacRumors says there was no evidence that the weak certificate keys had been exploited maliciously.

The exception matters to people using macOS command-line tools, including system administrators. MacRumors says some of those tools can continue accepting the certificates until Apple releases an update. Its documented workaround is to remove the affected certificates from the cert.pem file.

That workaround changes a command-line trust file. I would first identify whether the Mac actually uses the affected tools. I would preserve a recoverable copy of the file before editing it. People who only use Safari, Mail and applications that use Apple's networking and security frameworks can rely on the automatic block described by MacRumors while waiting for the additional update.

What can a Mac user do today?

Today, install macOS 27.2, inspect Activity Monitor if the Mac is hot or losing battery, and leave the PowerLog database alone unless dasd remains persistently high. For the shipped security work, install macOS 27.2 after checking essential applications, because the SecurityWeek account identifies that release as fixing 263 flaws on Mac computers today.

If dasd stays near the usage described in the report, make a Time Machine backup before considering the database workaround. OS X Daily warns that deleting an actively written system file can go wrong. A restart and Safe Mode did not help in its case, so repeating those steps indefinitely is not a documented fix.

If command-line certificate trust matters to your work, review the affected cert.pem file and the MacRumors workaround. Otherwise, use the automatic protection already applied to Safari, Mail and framework-based applications, and check Apple's release notes for the additional macOS update.

I would also record the installed release and the observed process usage before changing anything. That creates a useful before-and-after check. For continuity, my previous Mac status report covers what had shipped immediately beforehand.