CVE-2019-16791

MEDIUMNVD 6.96.9—

6.9

In postfix-mta-sts-resolver before 0.5.1, All users can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy.

CVSS v3: 6.9
EG Score: 6.9(medium)
EPSS: 53.6%
KEV: Not listed

Published

January 22, 2020

Last Modified

November 21, 2024

References (4)

security-advisories@githubhttps://gist.github.com/Snawoot/b9da85d6b26dea5460673b29df1adc6b
security-advisories@githubhttps://github.com/Snawoot/postfix-mta-sts-resolver/security/advisories/GHSA-h92m-42h4-82f6
af854a3a-2127-422b-91ae-364da2661108https://gist.github.com/Snawoot/b9da85d6b26dea5460673b29df1adc6b
af854a3a-2127-422b-91ae-364da2661108https://github.com/Snawoot/postfix-mta-sts-resolver/security/advisories/GHSA-h92m-42h4-82f6

Affected Packages

(1 across 1 ecosystem)

PyPI(1)

Package	Vulnerable range	Fixed in	Dependents
postfix-mta-sts-resolver	0.1.1 ... 0.5.0 (22 versions)	0.5.1	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-757

Data Freshness Timeline

(refreshed 10× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 08:51 UTCEG score recompute
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 22:56 UTCOSV refresh

Frequently asked(5)

What is CVE-2019-16791?

CVE-2019-16791 is a medium vulnerability published on January 22, 2020. In postfix-mta-sts-resolver before 0.5.1, All users can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy.

When was CVE-2019-16791 disclosed?

CVE-2019-16791 was first published in the National Vulnerability Database on January 22, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-16791 actively exploited?

CVE-2019-16791 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-16791?

CVE-2019-16791 has a CVSS v3 base score of 6.9 (NVD).

How do I remediate CVE-2019-16791?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-16791, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-16791

Explore →

Is Your Infrastructure Affected by CVE-2019-16791?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2019-16791

📅 Published

🔄 Last Modified

🔗 References (4)

Affected Packages

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-16791?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)