Loading vulnerability…
CVE-2025-42599 is a critical stack-based buffer overflow vulnerability in Active! mail 6 affecting BuildInfo 6.60.05008561 and earlier. The flaw can be triggered when the server processes a specially crafted request sent to a vulnerable Active! Mail instance. Successful exploitation by a remote, unauthenticated attacker may result in arbitrary code execution on the target server or cause the service to crash, leading to denial of service. The vulnerability has been reported as actively exploited.
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.
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical stack-based buffer overflow vulnerability in Qualitia Active! mail 6 that allows remote unauthenticated attackers to execute arbitrary code or cause denial of service.
A stack-based buffer overflow vulnerability in Active! Mail that allows remote code execution or denial-of-service via crafted requests.
Critical stack-based buffer overflow vulnerability in Active! Mail that allows remote unauthenticated code execution and can also cause denial of service.
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.