Mac bugs and fixes October 27 2026: what shipped
Chapters
TL;DR
Mac command-line tools could still accept compromised eMudhra certificates after weak keys were disclosed, MacRumors reported on October 25, 2026. The Mac bugs and fixes October 27 2026 status is mixed: 9to5Mac reported on October 26, 2026 that macOS 27.2 shipped as build 26B123. SecurityWeek reported on October 27 that the release fixes 163 Mac vulnerabilities, but no shipped fix is named for the command-line certificate gap or runaway dasd process.
- 9to5Mac identifies macOS 27.2 build 26B123 as the current release.
- SecurityWeek says macOS 27.2 fixes 163 Mac vulnerabilities.
- MacRumors says some command-line tools can still accept the compromised certificates.
- OS X Daily offers a risky
dasdworkaround that requires a backup and Terminal.
Did macOS 27.2 ship a fix?
Yes. 9to5Mac reported that macOS 27.2 shipped as build 26B123. The report says people with beta updates enabled might need to disable them before the final build appears in Software Update. I would check the build number rather than assume an earlier release candidate is current.
SecurityWeek, in its October 27 report, says macOS 27.2 fixes 163 flaws across WebKit, the kernel, images, fonts, PDFs, audio, video, and other components. SecurityWeek also attributes privacy bypasses, sandbox escapes, Gatekeeper bypasses, privilege escalation defects, and remotely reachable Screen Sharing, Remote Management, and SMB flaws to the repaired set.
The 9to5Mac account also describes earlier reports of Electron-based app windows refusing drag attempts, with a Mac restart providing only temporary relief before the behavior could return. The source names build 26B123 as the final release, but it does not provide a separate fix identifier for the dragging behavior. I would install the final build before spending time on repeated restarts. These macOS bugs do not share one status: the security repairs shipped, while some behavior-specific documentation remains incomplete.
For continuity, my Mac status from the previous day covers the position immediately before the final release became the useful dividing line.
Which Mac problems remain unfixed?
No shipped fix is named for the command-line certificate exception. MacRumors says Apple has automatically blocked the compromised eMudhra certificates in Safari, Mail, and apps using Apple networking and security frameworks since October 19. MacRumors adds that some macOS command-line tools can still accept those certificates until Apple releases a macOS update with a fix.
MacRumors says command-line users can remove the affected certificate from the cacerts.pem file, while noting that macOS does not use that file by default. That missing command-line protection still needs a macOS update fix. I would not edit a certificate store unless I knew which tool depended on it and had recorded the original configuration.
The Mac Observer, published October 21, says the macOS 27.2 release candidate could omit notification prompts after a clean installation for Calendar, Maps, Find My, Home, and Weather. The Mac Observer also says external-display settings might not restore correctly and the display arrangement might change. Apple’s listed notification workaround was System Settings > Notifications, while no workaround was listed for the display issue.
Those notes describe the release candidate, not build 26B123. No supplied source confirms whether either issue remains in the final release. The RC notes remain useful as a Mac known issues checklist, but I would not present them as confirmed final-build defects.
Is there a shipped fix for high dasd CPU use?
No vendor fix is named. OS X Daily, published October 26, describes dasd consuming 100% CPU on macOS 27. The author associated the behavior with telemetry and the PowerLog background-processing database after restart, Activity Monitor, and Safe Mode did not resolve the specific case.
OS X Daily says backing up and erasing the PowerLog database, followed by a restart, returned dasd to 0% CPU in the author’s case. The report warns that the procedure uses Terminal to delete a system file while the file is actively being written, so something could go wrong.
I would first confirm the process in Activity Monitor and restart the Mac. If dasd remains at the reported level, I would make a complete backup before considering the database reset. The workaround costs time, requires Terminal, removes an actively used system database, and carries an explicit risk of failure. It is not an Apple-issued repair.
No supplied source names an Apple acknowledgement, fixed build, or point release for the dasd behavior. I would stop before the deletion step if the backup could not be verified.
What can a Mac user do today?
Install macOS 27.2 build 26B123 after making a current backup, then verify the installed build. If Software Update shows an earlier release candidate, turn off beta updates and check again. The 9to5Mac report says beta updates might need to be disabled before build 26B123 appears.
AppleInsider, published October 26, says the update can be requested through System Settings > General > Software Update. AppleInsider recommends waiting at least a few days after a macOS update. That is a fair precaution for a work Mac, but waiting silently is not a complete plan.
SecurityWeek’s October 27 account identifies 163 repaired Mac flaws, including remotely reachable defects and flaws affecting sensitive data, privacy preferences, Gatekeeper, sandboxing, and root access. I would weigh those documented repairs against the applications and peripherals required for work. Treat macOS 27.2 as an Apple security update, not merely a cosmetic release.
After updating, test window dragging in Electron-based apps. Check System Settings > Notifications after a clean installation. Check System Settings > Displays if an external screen moves or loses settings. Command-line users should review the MacRumors certificate warning before relying on affected trust stores. For persistent dasd use, verify a backup before considering OS X Daily’s database reset.