Loading vulnerability…
CVE-2025-25198 affects mailcow: dockerized prior to version 2025-01a. The password reset functionality improperly trusts the incoming HTTP Host header when generating password reset URLs. An attacker can manipulate the Host header so that the application creates a reset link pointing to an attacker-controlled domain instead of the legitimate mailcow instance. If a victim uses the poisoned reset link, the attacker can capture the reset token or otherwise abuse the reset flow, leading to account takeover.
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.
Notification email sender and Notification email subject under System -> Configuration -> Options -> Password Settings. Additional defensive measures may include enforcing a trusted reverse proxy configuration and rejecting unexpected Host headers at the web server or proxy layer.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.