Urgent.News

What's breaking now, across thousands of outlets.

Tech

macOS Tahoe 26.4 update stops you from copying your login Keychain

Apple's changes to the Keychain in macOS Tahoe made it more secure. However, by binding it to device-specific Secure Enclave keys, users now can't manually copy the login Keychain and use it on another Mac. Password versioning in Apple Passwords Attacks on Mac users are getting more sophisticated over time, with AI also opening the door to even more malware and the discovery of new intrusion…

macOS Tahoe 26.4 update stops you from copying your login Keychain

Apple has released security updates for macOS 27 Golden Gate, macOS Tahoe 26.7, and macOS Sequoia 15.8, addressing over 200 vulnerabilities. These updates target a variety of issues, including those that could allow malicious apps to execute arbitrary code with kernel or root privileges, escape system protections, bypass Gatekeeper, modify critical system files, access sensitive user data, and more.

For instance, Apple patched a flaw in AVEVideoEncoder that could enable a sandboxed app to execute arbitrary code with kernel privileges. Similarly, a vulnerability in UDF file system could allow an app to execute code at the kernel level. The updates also address several vulnerabilities that could enable remote code execution through Bluetooth, CUPS, and WebDAV.

Both macOS Tahoe 26.7 and macOS Sequoia 15.8 contain many of the same fixes as macOS 27, with additional patches for macOS Sequoia 15.8, such as an ImageIO vulnerability that could lead to arbitrary code execution when processing a malicious image.

The full security changelogs for each update are available for those who wish to review the specific vulnerabilities addressed.

Written by urgent.news from 9to5Mac's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at appleinsider.com →

More in Tech

FAQ: Which Binary Did python Hit?

Ever trust a chat that said tests passed? Then watch the import fail on the box? The chat summary still looks clean and final. The binary on disk is a different story.

More from Sunday 13 September →