Update 08-11-august-cumulative-update.md

[TaraOverfield]

Summary

Add known issues

Fixes #Issue_Number (if available)

---

Internal previews

File	Preview link
docs/framework/release-notes/2026/08-11-august-cumulative-update.md	Preview published page

[Copilot]

Pull request overview

This PR updates the .NET Framework August 2026 cumulative update release notes to reflect a post-release edit that adds a newly identified known issue and workaround information.

Changes:

• Updates frontmatter ms.date and adds an “Updated” note under the release date.
• Replaces the empty “Known issues” section with a specific WPF printing/PDF/XPS issue, workaround guidance, and status.

Suppressed comments (1)

docs/framework/release-notes/2026/08-11-august-cumulative-update.md:62

• Use “might” (not “may”) for possibility to match the repo’s Markdown writing-style guidance.

This switch disables security protections introduced in the August 2026 update and may increase exposure to the vulnerabilities addressed by that update. Microsoft recommends using this workaround only as a temporary measure and only when required to address this issue.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[gewarren]

Suggested change

	**Workaround:** Applications can mitigate the issue by enabling the `Switch.MS.Internal.TtfDelta.DisableCmapAndSbitOverflowProtection` AppContext switch in the app config file, as shown below.
	**Workaround:** Applications can mitigate the issue by enabling the `Switch.MS.Internal.TtfDelta.DisableCmapAndSbitOverflowProtection` AppContext switch in the `app.config` file:

[gewarren]

Suggested change

	This switch disables security protections introduced in the August 2026 update and may increase exposure to the vulnerabilities addressed by that update. Microsoft recommends using this workaround only as a temporary measure and only when required to address this issue.
	This switch disables security protections introduced in the August 2026 update and might increase exposure to the vulnerabilities addressed by that update. Microsoft recommends using this workaround only as a temporary measure and only when required to address this issue.