CVE-2006-7039: The IMAP4 service in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a denial of

Routine

MEDIUM 5.0DOWNGRADE

CVE-2006-7039 is a medium-severity flaw (CVSS 5.0) affecting mercur messaging 2005. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The IMAP4 service in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a denial of service (crash) via a message with a long subject field.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Published	2007-02-23
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: atrium software

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2007-02-23 03:28 UTCPublished CVE record published
2026-06-16 22:34 UTCUpdated Record last modified

atrium software mercur messaging 2005 DOWNGRADE

Affected: 5.0_sp3

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.0_sp3

1. Check installed version

apt-cache policy mercur-messaging-2005 || rpm -q mercur-messaging-2005 || mercur-messaging-2005 --version

2. No fixed release: DOWNGRADE to a release before 5.0_sp3 (Debian / Ubuntu)

apt-cache madison mercur-messaging-2005 sudo apt install mercur-messaging-2005=<VERSION_BEFORE_5.0_sp3> sudo apt-mark hold mercur-messaging-2005

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mercur-messaging-2005 sudo dnf downgrade mercur-messaging-2005-<VERSION_BEFORE_5.0_sp3> sudo dnf versionlock add mercur-messaging-2005

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2006-7039?

mercur messaging 2005: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2006-7039 being exploited?

CVE-2006-7039 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2006-7039 affect?

CVE-2006-7039 affects mercur messaging 2005. Severity is medium (CVSS 5.0). The IMAP4 service in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a denial of service (crash) via a message with a long subject field.

How urgent is CVE-2006-7039?

Priority 36/100. No elevated risk signals yet.

Related CVEs

CVE-2007-1579 HIGH 10.0 MITIGATE DOWNGRADE Stack-based buffer overflow in Atrium MERCUR IMAPD allows remote attackers to have an unknown impact via a cer
CVE-2006-7041 HIGH 7.8 DOWNGRADE The SMTP service in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a denial of s
CVE-2006-7040 HIGH 7.8 DOWNGRADE Unspecified vulnerability in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a de
CVE-2006-7038 HIGH 7.8 DOWNGRADE Multiple buffer overflows in MERCUR Messaging 2005 before Service Pack 4 allow remote attackers to cause a den

References

← Back to latest CVEs