Loading story…
Microsoft published Security Update Guide entries for CVE-2026-26176 and CVE-2026-34276, adding two newly tracked vulnerabilities to its advisory catalog. The available references identify both issues by CVE and confirm their inclusion in Microsoft's official vulnerability portal, but do not provide public synopsis text or technical details on affected products, severity, exploitation status, or remediation steps.
The disclosures indicate that organizations monitoring Microsoft risk exposure should track both CVEs for follow-on guidance, including patch availability, product impact, and any changes to exploitability assessments. Until fuller advisory content is published, defenders should treat CVE-2026-26176 and CVE-2026-34276 as newly disclosed Microsoft vulnerabilities requiring validation against asset inventories and routine update management processes.
See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
Microsoft added CVE-2026-34276 to its Security Update Guide. No further synopsis or event details are provided in the reference.
Microsoft added CVE-2026-26176 to its Security Update Guide. No further synopsis or event details are provided in the reference.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Microsoft published Security Update Guide entries for **CVE-2026-35236** and **CVE-2026-35238**, adding two newly tracked vulnerabilities to its official advisory catalog. The entries were released through the Microsoft Security Response Center (MSRC) and indicate that both issues are being handled as formal security cases requiring vendor guidance and patch tracking. The advisories currently provide limited public detail beyond the identifiers and their publication in Microsoft's update portal, leaving affected product scope, severity, and exploitation context unclear from the available references. Organizations that rely on Microsoft platforms should monitor the MSRC pages for expanded technical information, affected-version mapping, and remediation guidance as Microsoft updates the records.
Jul 12, 2026
Microsoft published Security Update Guide entries for **`CVE-2025-67030`** and **`CVE-2026-21716`**, adding two newly tracked vulnerabilities to its advisory catalog. The references indicate both issues were disclosed through Microsoft's official vulnerability portal, with one entry tied to a 2025 CVE identifier and the other to a 2026 identifier. The available records provide only limited public detail, listing the CVE identifiers and publication through the Microsoft Security Response Center without a synopsis or technical description. Organizations that rely on Microsoft products should monitor the corresponding advisory pages for severity, affected products, exploitability information, and patch guidance as Microsoft updates the entries.
Jul 12, 2026
Microsoft added **`CVE-2026-23279`** and **`CVE-2026-23300`** to its Security Update Guide, publishing advisory entries through the Microsoft Security Response Center (MSRC). The available references indicate both vulnerabilities were formally disclosed as Microsoft security advisories, but the public entries provided no synopsis or technical summary at the time of publication. The limited disclosure leaves affected products, impact, and exploitation details unclear from the referenced advisories alone. Organizations that rely on Microsoft software should track the MSRC entries for updates, validate whether either **CVE** applies to their environment, and prepare to prioritize patching or mitigations once Microsoft publishes fuller technical guidance and remediation details.
Jul 12, 2026