Apple Releases macOS Tahoe 26.6.2 Security Update: 28 CVEs, Build 25G83, and What to Do

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Original editorial illustration of a Mac security update screen for macOS Tahoe 26.6.2 build 25G83, with a calm Windows status display in the background — Original editorial illustration. Apple released macOS Tahoe 26.6.2, build 25G83, on August 17, 2026; Windows had no new production OS patch today.

Apple released macOS Tahoe 26.6.2 on August 17, 2026, as a public production security update. The release is build 25G83, and Apple’s security bulletin lists 28 unique CVE identifiers across WebKit, the kernel, ImageIO, Audio, and graphics components. If your Mac already runs Tahoe, this is the update to install after a normal backup and compatibility check.

Security release • macOS Tahoe only • Build 25G83

Bottom line: This is not a beta, a Rapid Security Response, or a generic documentation refresh. Apple’s public security-release table and consumer update notes now confirm the production release. Apple did not say any of the listed vulnerabilities are being actively exploited, but several involve arbitrary code execution, kernel memory, sensitive data, or malicious web content—good reasons not to postpone the update indefinitely.

What Apple released today

Apple’s dedicated security bulletin says these fixes were first made available in the macOS Golden Gate 27 beta and are now delivered to macOS Tahoe users through version 26.6.2. Apple’s Developer Software Releases catalog identifies the production build as 25G83. Apple’s general Tahoe update notes describe 26.6.2 simply as an update that “provides security fixes for your Mac.”

Phone readers: swipe the table left to see every column.

Item	Verified detail	What it means
Version	macOS Tahoe 26.6.2	A public update for Macs already on Tahoe 26.
Build	25G83	The build number you can verify after installation.
Release date	August 17, 2026	A same-day production release, not older context.
Security inventory	28 unique CVE IDs listed by Apple	Applicability varies by component; this is not a claim that every Mac was exposed to every bug.
Active exploitation	Not stated by Apple	Do not call these zero-days without additional evidence.
Older macOS branches	No new Sequoia or Sonoma release dated August 17	The newest listed updates for those branches remain 15.7.9 and 14.8.9 from August 6.

The most important security fixes

Apple’s bulletin covers more than browser crashes. The practical risk depends on what a user opens, what software runs locally, and whether an attacker can reach the affected interface.

ImageIO
Apple says a crafted image could trigger arbitrary code execution through CVE-2026-65346. A separate ImageIO issue could cause a denial of service.

Kernel
Apple documents a remote path to unexpected system termination, plus local-app paths that could read or corrupt kernel memory or crash the Mac.

WebKit and web content
The bulletin lists multiple memory-corruption, use-after-free, crash, termination, and sensitive-data issues associated with maliciously crafted web content or websites.

Audio and graphics
An Audio logic issue could leak sensitive information, while an IOGPUFamily flaw could allow malicious web content to cause memory corruption.

The CVE total is a bulletin-level count. It should not be interpreted as 28 separate attacks that are active in the wild, nor as 28 fixes that every user could independently trigger. Apple has not attached an active-exploitation warning to this release.

Who is affected—and who is not

Your device	Status	Action
Mac running macOS Tahoe 26.x	Affected release family	Back up, check Software Update, and install 26.6.2 when it is offered.
Mac already on 26.6.2 / build 25G83	Current for this release	Restart if requested, then verify the version and build.
Mac on Sequoia 15.x or Sonoma 14.x	Not covered by this 26.6.2 bulletin	Do not force-install Tahoe solely because of this article. Install the latest update Apple offers for your supported branch.
Mac that cannot upgrade to Tahoe	Compatibility-dependent	Stay on the newest supported branch available for that hardware and review Apple’s security-release table.
Windows PC	Not affected by this macOS release	Use Windows Update normally; there was no new production Windows OS patch dated August 17.

How to check and update your Mac safely

Save your work and make a current backup. Time Machine or another tested backup is better than discovering a failed update with no recovery path.
Open System Settings → General → Software Update. Confirm that the offered item is macOS Tahoe 26.6.2 before approving it.
Keep the Mac on power and a stable connection. Do not interrupt firmware or operating-system installation.
Restart when prompted. Some security changes are not fully active until the update and restart complete.
Verify the result. Choose Apple menu → About This Mac, or open Terminal and run sw_vers -productVersion and sw_vers -buildVersion. The expected results are 26.6.2 and 25G83.

If 26.6.2 does not appear: Do not download an installer from a search ad or an unofficial mirror. Confirm that the Mac is already on Tahoe, restart once, check date/time and available storage, and try Software Update again. Business-managed Macs may intentionally delay updates through MDM policy.

Business and managed-fleet actions

Confirm 26.6.2 appears in the organization’s MDM/software-update inventory before forcing a broad rollout.
Pilot the update on representative Intel and Apple-silicon hardware actually used by the business, including VPN, endpoint security, printing, accounting, and line-of-business software.
Record the pre-update version, post-update version, and build 25G83 so “installed” can be distinguished from “downloaded” or “restart pending.”
Use phased deployment rings, monitor support tickets and vendor advisories, and keep a rollback or recovery plan for critical workstations.
Prioritize higher-risk users who regularly handle untrusted images, email attachments, or web content, while still respecting application-compatibility holds.

Known issues and installation cautions

Apple’s public 26.6.2 security bulletin and general update note do not list release-specific known issues. That absence is not a promise that every third-party application, driver, peripheral, or security tool will behave perfectly. Check vendor guidance for mission-critical software, maintain enough free storage, and avoid beginning the update immediately before travel, a deadline, or an important meeting.

Good
The production status is now unambiguous; Apple published a dedicated security bulletin, a public release-table entry, consumer update notes, and build 25G83. The release covers high-impact classes including image code execution and kernel memory problems.

Bad / caution
Apple provides little consumer-facing detail about real-world likelihood, and no release-specific known-issues list. Older macOS branches did not receive a new same-day companion update in the security table.

Windows check: no new production patch, but one server reminder

Microsoft did not release a new Windows 11, Windows 10, or Windows Server production cumulative update on August 17. The newest production security updates remain the August 11 Patch Tuesday releases. Same-day Windows Insider builds are previews and should not be mistaken for production fixes.

Microsoft did publish a 60-day operational reminder for organizations running Active Directory Federation Services. It concerns DKM-container access-control hardening for CVE-2026-56155 ahead of the October 13 enforcement change. That is important for AD FS administrators, but it is not a new consumer Windows patch—and The IT Guys already published a detailed AD FS DKM hardening guide, so we are not duplicating it tonight. For the broader Windows baseline, see our August 2026 Patch Tuesday guide.

FAQ

Is macOS Tahoe 26.6.2 an emergency zero-day update?

Apple released it as a security update, but its bulletin does not say the listed flaws are being actively exploited. “Security update” is accurate; “active zero-day emergency” is not supported by Apple’s published information.

Is build 25G83 still a beta?

No. A pre-release 26.6.2 build appeared earlier, but Apple’s public security table, consumer update notes, and production developer release entry now corroborate 26.6.2 build 25G83 as a public production release.

Do Sequoia and Sonoma users get 26.6.2?

No. Version 26.6.2 belongs to Tahoe. Sequoia and Sonoma users should install the newest update offered for their own supported branch rather than trying to apply a Tahoe-specific package.

Does Safari receive the WebKit fixes automatically?

The WebKit fixes are documented as part of macOS Tahoe 26.6.2. Install the operating-system update and restart as requested; do not assume that merely closing and reopening Safari applies the full OS update.

Should a business deploy it to every Mac immediately?

Security urgency and operational risk need to be balanced. A short, controlled pilot followed by phased deployment is safer than either indefinite delay or an untested all-at-once push.

What if Software Update shows a different version?

Stop and confirm the current macOS branch and hardware compatibility. Apple can offer branch-specific updates, and managed devices may follow an organizational deferral. Use Apple’s official Software Update interface rather than third-party download sites.

Official sources

Browse more Apple coverage