Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-10140: Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local user

44
This month
HIGH 7.8UPGRADE

CVE-2017-10140 is a high-severity flaw (CVSS 7.8) affecting postfix. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and later, related to reading settings from DB_CONFIG in the current directory.

Why this priority

  • High severity
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.5% (top 54%)
CISA exploited listNo
Published2018-04-16
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: postfix

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

postfix postfix UPGRADE
Affected: < 2.11.10 · >= 3.0.0 and < 3.0.10 · >= 3.1.0 and < 3.1.6 · >= 3.2.0 and < 3.2.2
Fixed in: 2.11.10, 3.0.10, 3.1.6, 3.2.2
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy postfix || rpm -q postfix || postfix --version
2. UPGRADE to 2.11.10 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade postfix
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade postfix
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison postfix sudo apt install postfix=<VERSION_BEFORE_3.0.0> sudo apt-mark hold postfix
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list postfix sudo dnf downgrade postfix-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add postfix
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-2017-10140?

postfix: upgrade to 2.11.10, 3.0.10, 3.1.6, 3.2.2. Exact commands for each OS are on this page.

Is CVE-2017-10140 being exploited?

CVE-2017-10140 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-2017-10140 affect?

CVE-2017-10140 affects postfix. Severity is high (CVSS 7.8). Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and later, related to reading settings from DB_CO

How urgent is CVE-2017-10140?

Priority 44/100. High severity; Public exploit reference

Software pages

Postfix vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.