[Patch Now] Microsoft March 2026: 79 CVEs, 2 Zero-Days | Tech Bytes

Microsoft March 2026 Patch Tuesday fixes 79 CVEs including 2 actively exploited zero-days in Windows kernel and NTFS. Update dev machines and build servers n...

Microsoft’s March 2026 Patch Tuesday addresses 79 CVEs. Two of those are actively exploited zero-days: one in the Windows kernel and one in NTFS. Kernel bugs sit under almost every privilege boundary on the machine. NTFS bugs sit under every local file operation, including installs, builds, and any process that touches disks or mount points. When both are under active attack, waiting for a “quiet week” is not a plan.

What happened

Start from exposure, not from the headline. What software, cloud service, or configuration is actually in the blast radius of [Patch Now] Microsoft March 2026: 79 CVEs, 2 Zero-Days | Tech Bytes? Write that list down before you open a war room. Most wasted hours on stories like this are spent debating severity before anyone knows whether they run the thing.

Microsoft March 2026 Patch Tuesday fixes 79 CVEs including 2 actively exploited zero-days in Windows kernel and NTFS. Two of those are actively exploited zero-days: one in the Windows kernel and one in NTFS.

Who is exposed

Anyone running the affected component in production, CI, or a laptop fleet is in scope until proven otherwise. Inventory first. Include forgotten staging clusters and contractor laptops — those are where 'we don't run that' turns out to be false.

Kernel bugs sit under almost every privilege boundary on the machine. NTFS bugs sit under every local file operation, including installs, builds, and any process that touches disks or mount points.

What to do now

Patch, rotate credentials, and confirm the vendor's fixed version from their advisory — not from a social recap. If you cannot patch today, isolate the service and raise the logging floor. Record the decision and the residual risk so the next person does not re-litigate it.

When both are under active attack, waiting for a “quiet week” is not a plan. What software, cloud service, or configuration is actually in the blast radius of [Patch Now] Microsoft March 2026: 79 CVEs, 2 Zero-Days | Tech Bytes?

How the issue works

Most incidents in this class are either an input-handling bug or a trust-boundary miss. Reconstruct the path with the advisory's affected-versions list in hand. If you cannot explain the path in three sentences, you do not understand it well enough to declare yourself safe.

Most wasted hours on stories like this are spent debating severity before anyone knows whether they run the thing. Anyone running the affected component in production, CI, or a laptop fleet is in scope until proven otherwise.

What is still unknown

What is still unknown is as important as what shipped. Track whether exploitation is confirmed, whether a CVE is assigned, and whether your WAF or EDR signatures have caught up. Revisit the ticket when any of those three flip.

Include forgotten staging clusters and contractor laptops — those are where 'we don't run that' turns out to be false. Patch, rotate credentials, and confirm the vendor's fixed version from their advisory — not from a social recap.

A 3–5 minute news post is a briefing, not a runbook. Keep Tech Bytes and the vendor's primary page in another tab, quote only what they printed, and write down the single decision this story forces (upgrade, wait, or ignore) before you Slack it to the rest of the team. If you need more than that decision, you want the primary docs or a later engineering deep-dive — not another recap of [Patch Now] Microsoft March 2026: 79 CVEs, 2 Zero-Days | Tech Bytes.

When you brief someone else on [Patch Now] Microsoft March 2026: 79 CVEs, 2 Zero-Days | Tech Bytes, lead with the surface that moved and the decision you need from them. Do not paste the whole thread. If you cannot name the surface — API, policy, model, hardware, or commercial terms — you are not ready to brief. Go back to Tech Bytes and the vendor page until you can. That extra ten minutes is cheaper than a wrong upgrade or a missed exposure.