Loading vulnerability…
A flaw in OpenSSL's POLY1305 MAC implementation on Windows 64-bit systems can corrupt application state when executed on newer x86_64 processors that support AVX512-IFMA instructions. During POLY1305 processing of input larger than 64 bytes, the affected implementation fails to preserve non-volatile XMM registers as required. Before returning to the caller, it zeroes those registers instead of restoring their prior contents. This can break assumptions made by the calling application and lead to state corruption outside the cryptographic routine itself. The issue is most relevant where an attacker can influence selection of POLY1305, commonly through CHACHA20-POLY1305 in TLS 1.2 or TLS 1.3 server contexts. Affected versions are OpenSSL 1.1.1 through 1.1.1v, 3.0.0 through 3.0.10, and 3.1.0 through 3.1.2. OpenSSL 1.0.2 and the FIPS provider are not affected.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OpenSSL POLY1305 MAC implementation flaw that corrupts XMM registers on Windows.
Unknown
A low-severity OpenSSL vulnerability in the POLY1305 MAC implementation on Windows x64 systems with AVX512-IFMA support that can corrupt application state by zeroing non-volatile XMM registers, potentially causing incorrect calculations, crashes, denial of service, or in worst cases application compromise.
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.