Loading story…
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.
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-21716 to its Security Update Guide. No further synopsis or technical details are provided in the reference.
Microsoft added CVE-2025-67030 to its Security Update Guide. No further synopsis or 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-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