Loading story…
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.
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-3731 to its Security Update Guide. No further technical details are provided in the reference.
Microsoft added CVE-2026-4444 to its Security Update Guide. No further technical 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-34714** and **CVE-2026-21713**, adding both vulnerabilities to its official advisory portal. The notices were issued through Microsoft's security advisories channel and indicate that the flaws have been formally tracked and disclosed under separate CVE identifiers. The available references provide only limited public detail beyond the existence of the two advisories, with no synopsis included in either entry. Organizations that rely on Microsoft products should monitor the corresponding Security Update Guide pages for affected components, severity information, and remediation guidance as Microsoft updates the records.
Jul 12, 2026
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-2023-36570** and **CVE-2023-36574**, adding the two identifiers to its official vulnerability tracking and remediation catalog. The references indicate both issues were documented through Microsoft's advisory infrastructure, though the provided entries do not include public synopsis details describing affected components, attack vectors, or impact. The disclosures signal that organizations relying on Microsoft products should review the corresponding Security Update Guide records for product scope, severity, and patch availability, then validate whether exposed systems are affected. Because the available references contain only the advisory listings, defenders should treat the CVEs as newly tracked Microsoft security issues pending fuller technical detail from the vendor's update guidance and associated patches.
Jul 12, 2026