Microsoft published Security Update Guide entries for CVE-2025-21369, CVE-2024-43638, and CVE-2024-49090, indicating vendor-tracked security issues affecting Microsoft products. The references point to official Microsoft advisory and vulnerability pages, but the available source material does not include vulnerability names, affected components, severity ratings, exploitation details, or remediation guidance.
The entries appear across Microsoft’s MSRC update and product advisory portals, showing that the CVEs were formally cataloged by the vendor as part of its security disclosure and patching process. Organizations that rely on Microsoft software should monitor the corresponding MSRC pages for technical details, affected-version information, and update availability as Microsoft expands or finalizes the advisories.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
Microsoft published a Security Update Guide vulnerability entry for CVE-2025-21369. No synopsis or supporting details were included in the provided reference.
Microsoft published a Security Update Guide vulnerability entry for CVE-2024-49090. The reference content does not include further details about impact, exploitation, or remediation.
Microsoft published a Security Update Guide advisory entry for CVE-2024-43638. No additional synopsis or technical details were provided in the reference content.
3 references tracked. Mallory keeps watching after this page renders.
msrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourceMap 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.