Mac bugs and fixes October 24 2026: no fix yet

What broke in macOS 27.2 Golden Gate RC?

Clean installations can miss app notification prompts, The Mac Observer says. The reported issue affects some apps after a Mac is erased and the build is installed fresh, or when a new Mac is set up on it. Calendar, Maps, Find My, Home and Weather are named as examples. The list is not necessarily complete because Apple describes the affected apps with the words “such as.”

An affected app might never ask for notification permission. Its alerts can therefore remain off without an obvious prompt explaining why. The documented workaround is manual. Open System Settings from the Apple menu, select Notifications, choose each affected app and turn its notifications on. I would also inspect any other app that should send alerts but remains silent after a clean installation.

The same release candidate carries external-display known issue 188643179. Display settings might not be restored correctly when an external display connects, and the display arrangement might change. Apple does not list a workaround. The report advises opening System Settings > Displays and checking each screen’s arrangement and settings.

Neither problem has a shipped fix in the cited report. macOS 27.2 Golden Gate remains a release candidate in that account. The notification procedure is a workaround, not evidence that Apple removed the underlying behavior. If it happens, open System Settings > Displays and check the arrangement and settings for each screen. Apple does not list a workaround.

Has Apple fixed the certificate vulnerability?

No macOS fix has shipped for the compromised-certificate trust gap, 9to5Mac says. Apple, Google and Mozilla blocked the affected certificates in their respective web browsers. The operating-system problem remains separate from those browser protections.

The report concerns intermediate certificates generated with an erroneous script. Private keys could be discovered by testing 256 possible numbers. Eight compromised certificates have been revoked, and measures were taken to prevent the same vulnerability from affecting future certificates from the issuer.

A Mac might continue trusting a certificate it already accepted because macOS does not check revocation information in the relevant path. The built-in /usr/bin/curl utility might also continue trusting the certificates because its certificate bundle does not check revocation information. The report says there is currently no evidence of exploitation in the wild.

A future Apple security update was presented as likely, not shipped. I would not treat the browser blocks as a complete operating-system repair. I also would not install an unrelated update and assume the trust gap has closed. A documented Apple release note is still needed before calling the macOS side fixed.

Which fixes have actually shipped?

Browser blocks are active, but no macOS certificate fix is documented, 9to5Mac says. That distinction matters. Blocking the compromised certificates in browsers limits one route, while the reported macOS and /usr/bin/curl trust behavior remains unresolved.

No operating-system repair is documented for the missing notification prompts either. Apple provides a manual settings workaround. The external-display issue has no listed Apple workaround, although checking System Settings > Displays can restore the arrangement and settings a person wants.

I therefore separate the current status into three categories. The certificate issue has browser mitigation but no cited macOS repair. Missing notification prompts have a manual workaround but no cited update fix. Changed display arrangements have a practical settings check but no Apple-listed workaround.

That is the useful reading of today’s macOS bugs. A mitigation is not the same as a fix, and a release candidate is not proof that a correction has reached ordinary Macs. Waiting silently gives the person at the keyboard no useful instruction. The published workarounds do.

What can a Mac user do today?

Manually enable missing notifications and inspect display arrangements today, following The Mac Observer’s documented checks. On a freshly installed Mac, open System Settings > Notifications. Review Calendar, Maps, Find My, Home and Weather. Turn on notifications for every affected app that should alert you.

The cost of that workaround is a manual review of each app. Alerts remain off until they are enabled. I would test an expected notification afterward rather than assume the setting took effect. I would also review any silent app outside Apple’s examples because the published list is not necessarily complete.

For an external display, open System Settings > Displays. Confirm where each screen sits in the arrangement and inspect the settings for every connected screen. The cost is the time needed to restore the preferred layout. Apple has not supplied a documented workaround for preventing the arrangement from changing again.

For the certificate issue, keep browser protections current, but do not call the Mac fixed. No supported local repair is cited for the remaining operating-system trust behavior. I would avoid relying on /usr/bin/curl for a sensitive connection involving the affected certificates until Apple documents a correction.

For continuity with the previous status, compare Mac bugs and fixes October 23 2026: what shipped. Record the current macOS build and any settings changed before troubleshooting. That gives you a clear rollback point for manual configuration, even though no vendor fix has shipped for the highlighted Mac known issues.