Microsoft Discloses Unpatched Defender ‘ShieldBreak’ Flaw: Update Edge and PowerShell Now

Microsoft disclosed an important Defender elevation-of-privilege vulnerability on August 14, but it did not release a fix with the advisory. The same day brought a security update for Microsoft Edge, corrected PowerShell 7 packages, and two October support-planning notices. There is no new Windows cumulative update today, and Apple did not publish a same-day macOS security release.

What Microsoft released—and what it did not

This is not Patch Tuesday, not an out-of-band Windows cumulative update, and not a new Windows build. Microsoft’s latest production Windows cumulative updates remain the August 11 Patch Tuesday releases. If you have not installed those yet, start with our practical guide to the August 2026 Windows Patch Tuesday updates.

August 14 instead produced three separate security actions: a newly disclosed Defender issue with no fix yet, an Edge Stable browser update, and revised PowerShell 7 packages. Microsoft also posted lifecycle reminders for Windows 11 24H2 Home and Pro, Windows 10 Enterprise LTSB 2016, and Windows Server 2022.

1. “ShieldBreak”: Defender flaw disclosed before a fix is available

CVE-2026-69414, publicly referred to as ShieldBreak, is an elevation-of-privilege vulnerability in the Microsoft Malware Protection Engine used by Microsoft Defender. Microsoft rates it Important with a CVSS 3.1 base score of 7.8.

• Publicly disclosed: Yes.
• Known exploitation: Microsoft says No as of the August 14 advisory.
• Exploitability assessment: “Exploitation More Likely.”
• Attack requirements: Microsoft’s CVSS vector describes local access by a low-privileged user, with no additional user interaction.
• Fix: None was listed at our 7 PM Eastern cutoff. Microsoft says it is preparing a security update and will update the CVE page when it is available.

That combination deserves attention but not panic. “More likely” is Microsoft’s exploitability assessment, not a statement that attacks are already occurring. The advisory also does not yet provide a detailed platform/version matrix, a workaround, or a fixed Defender engine version. Do not invent one from a social-media post or an unrelated Defender definition number.

Who should treat ShieldBreak as relevant?

What to do while Defender has no listed fix

1. Keep Defender on. Disabling malware protection is not a mitigation for an elevation-of-privilege flaw; it simply removes a defensive layer.
2. Install current Windows updates. ShieldBreak is separate from the August 11 cumulative update, but an unpatched Windows system gives an attacker more options.
3. Reduce local administrator use. Use a standard account for ordinary work and a separate administrative account only when needed.
4. Be strict about downloads and remote access. The CVSS vector indicates that an attacker first needs local low-privileged access. Do not run unexpected installers, scripts, “support tools,” or cracked software.
5. Watch Microsoft’s CVE page. The correct fixed version must come from Microsoft’s updated advisory—not guesswork.
6. Businesses should prepare deployment now. Inventory endpoints, confirm Defender health reporting, identify devices that miss protection updates, and have a pilot group ready when the fix arrives.

2. Microsoft Edge 151.0.4129.86 fixes an Important RCE flaw

Microsoft released Edge Stable 151.0.4129.86 on August 14. It fixes the Edge-specific CVE-2026-72970, an Important heap-buffer-overflow remote-code-execution vulnerability with a CVSS base score of 8.3. Microsoft says the flaw was neither publicly disclosed nor known to be exploited when the update shipped.

The release also incorporates Chromium security fixes. Browser patches matter quickly because a malicious or compromised web page can be enough to start an attack chain. Microsoft’s advisory says user interaction is required; that does not make an outdated browser safe.

How to verify your Edge version

1. Open Microsoft Edge.
2. Select the three-dot menu, then Help and feedback → About Microsoft Edge.
3. Let Edge check for updates.
4. Confirm the version is 151.0.4129.86 or later.
5. If Edge asks to restart, save your work and restart the browser. Reopen the About page to confirm the running version.

Managed organizations should also confirm deployment in their browser-management console. A policy that permits updates is not proof that every laptop has received and launched the new build.

3. PowerShell 7 users need revised fixed packages

Microsoft revised five August PowerShell advisories on August 14 and updated the security packages. The fixed versions are:

• PowerShell 7.4.19 for the supported 7.4 branch;
• PowerShell 7.5.10 for the 7.5 branch; and
• PowerShell 7.6.5 for the 7.6 branch.

The five advisories cover information disclosure, elevation of privilege, remote code execution, and a security-feature bypass: CVE-2026-58612, CVE-2026-59119, CVE-2026-70337, CVE-2026-70338, and CVE-2026-50523.

Open PowerShell 7 and run:

pwsh --version

If you are on an older 7.4, 7.5, or 7.6 build, update through the same trusted channel used to install it—such as the official Microsoft package, Microsoft Store, Windows Package Manager, or your organization’s software-management system. Windows PowerShell 5.1 and PowerShell 7 are different products; seeing “Windows PowerShell” in the Start menu does not prove that PowerShell 7 is installed.

October 13 support reminders: important, but not new patches

Microsoft’s Windows Message Center posted two planning notices on August 14:

• Windows 11 version 24H2 Home and Pro and Windows 10 Enterprise LTSB 2016 reach end of updates on October 13, 2026. Windows 11 24H2 Enterprise and Education have a different lifecycle and remain supported longer. Eligible Home/Pro systems should plan for Windows 11 25H2.
• Windows Server 2022 reaches the end of mainstream support on October 13. It does not lose security updates that day; extended support continues through October 14, 2031. Businesses should still evaluate Server 2025 for workloads that need full mainstream support.

These notices do not replace yesterday’s edition-specific guidance. If you manage Enterprise or Education PCs, read our Windows 11 23H2 Enterprise and Education support guide as well.

What about today’s Windows Insider builds?

Microsoft released new Release Preview builds on August 14: KB5120998 for Windows 11 24H2/25H2 and KB5120996 for 26H1. Microsoft labels them non-security previews. They are test builds, not production security patches, and ordinary home or business PCs should not join the Insider program just to obtain them.

Apple/macOS check: no August 14 production release

Apple’s official security-release table showed no same-day macOS security update, Rapid Security Response, or Background Security Improvement. The latest public security releases remain macOS Tahoe 26.6.1, macOS Sequoia 15.7.9, and macOS Sonoma 14.8.9, all dated August 6. Those older updates addressed a Screen Sharing authentication vulnerability and remain worth installing if a Mac has missed them, but they are not new August 14 releases.

Apple’s developer release catalog lists macOS 26.6.2 dated August 10, while the public security index and general Tahoe update notes checked tonight still stop at 26.6.1. We are treating that mismatch as a documentation/status caveat—not inventing a same-day public security release.

Good news and caution

FAQ

Is ShieldBreak being actively exploited?

Microsoft marked CVE-2026-69414 as publicly disclosed and “Exploitation More Likely,” but said it was not known to be exploited as of August 14. Those labels can change; use the live MSRC advisory as the authority.

Should I turn off Microsoft Defender?

No. Turning off Defender removes malware protection and is not listed by Microsoft as a workaround. Keep it enabled and current while waiting for Microsoft’s security update.

Does Windows Update fix ShieldBreak today?

Microsoft had not listed a fix in the CVE at our cutoff. The August 11 cumulative Windows update remains important, but it should not be described as the ShieldBreak fix.

Does Edge update automatically?

Usually, but “automatic” can be delayed by a browser that stays open, a powered-off laptop, a management policy, or a failed update service. Open About Microsoft Edge and confirm 151.0.4129.86 or later.

How do I know whether I have PowerShell 7?

Run pwsh --version. If the command is not found, PowerShell 7 may not be installed or may not be in your path. Windows PowerShell 5.1 uses a different executable and lifecycle.

Is Windows Server 2022 unsafe after October 13?

No. October 13 is the end of mainstream support, not the end of security updates. Extended support continues through October 14, 2031. The planning concern is reduced mainstream servicing and the need to modernize on a controlled schedule.

Official sources

• Microsoft Security Response Center: CVE-2026-69414
• Microsoft Edge security release notes for August 14, 2026
• MSRC August 2026 CVRF security document
• Windows Message Center
• Windows 11 release information
• Windows 10 release information
• Windows Server release information
• Windows Insider: August 14 Release Preview builds
• Apple security releases
• Apple Background Security Improvements by date

Checked against official Microsoft and Apple sources at 7 PM Eastern on August 14, 2026. Security status can change; live vendor advisories control.