CVE-2025-3576 is a cryptographic-integrity vulnerability in MIT Kerberos affecting GSSAPI-protected messages that use the legacy RC4-HMAC-MD5 encryption type. The mechanism relies on MD5-based checksums whose collision resistance is insufficient for message-authentication use. An attacker able to exploit MD5 collision weaknesses can forge a message integrity code for altered or spoofed GSSAPI messages when RC4-HMAC-MD5 is negotiated.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability involving forgeable RC4-HMAC-MD5 checksums in MIT Kerberos when RC4 is enabled.
A vulnerability addressed through the OADP must-gather backport; no further technical details are provided.
Unknown
Unknown
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.