Loading story…
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.
See real exploitation activity before you spend the cycle.
1 event from the most recent confirmed update back to the earliest known activity.
Microsoft's Security Update Guide lists vulnerability entries for CVE-2026-23279 and CVE-2026-23300. No additional synopsis or event details are provided in the references beyond their publication in the advisory portal.
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-23368`** and **`CVE-2026-23274`**, adding both vulnerabilities to its official advisory portal. The entries were listed by the Microsoft Security Response Center (MSRC), indicating the flaws have been formally tracked and disclosed through Microsoft's standard vulnerability management process. The available references provide only limited public detail, with the advisory pages showing no synopsis in the source material. Even so, the publication of two distinct CVE records signals that affected Microsoft products or components may require review as organizations monitor MSRC for severity ratings, impacted software details, update availability, and any associated mitigation guidance.
Jul 12, 2026
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-2026-3731`** and **`CVE-2026-4444`**, adding the vulnerabilities to its official advisory portal. The available references identify both issues by CVE and confirm they were disclosed through Microsoft's security advisory process, but do not provide public synopsis details in the cited entries. The disclosures indicate that organizations tracking Microsoft risk should review the corresponding Security Update Guide records for affected products, severity, and remediation guidance as those details become available or are updated. In the referenced material, **`CVE-2026-3731`** appears in an advisory published on 2026-03-11, while **`CVE-2026-4444`** appears in an advisory published on 2026-01-01.
Jul 12, 2026