Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2007-2187: Stack Buffer Overflow in eXtremail DNS Response Handling

Published Apr 24, 2007 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS6.9%94th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Extremail
IdentifiersCVE-2007-2187CWE-121

A stack-based buffer overflow exists in eXtremail 2.1.1 and earlier, triggered by processing a long DNS response. The vulnerability allows remote attackers to overflow a stack buffer, potentially leading to arbitrary code execution. The flaw is in the DNS response handling code, which does not properly validate the length of incoming DNS responses before copying them to a stack buffer.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code with the privileges of the eXtremail process, potentially leading to full system compromise.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the eXtremail service to trusted hosts only. Employ network-level protections such as firewalls or intrusion prevention systems to block malicious DNS responses. Monitor for abnormal DNS traffic targeting the eXtremail server.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of eXtremail that properly validates DNS response lengths before copying data to stack buffers. If no patch is available, consider disabling or restricting DNS-based functionality in eXtremail.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ExtremailExtremailapplication
FAQ

Frequently asked questions

Is CVE-2007-2187 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2007-2187 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2007-2187?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2007-2187.
Is there a patch for CVE-2007-2187?
Upgrade to a patched version of eXtremail that properly validates DNS response lengths before copying data to stack buffers. If no patch is available, consider disabling or restricting DNS-based functionality in eXtremail.
What products are affected by CVE-2007-2187?
Extremail.
How severe is CVE-2007-2187?
CVE-2007-2187 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 6.9% (94th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.