Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The postfix-mta-sts-resolver package, versions before 0.5.1, can return an incorrect response from its daemon under rare conditions, which downgrades the effective MTA-STS policy. The source gives few details on the exact trigger or what an attacker must do to exploit it. Upgrade to version 0.5.1, which contains the fix; the advisory's linked patches for older versions are an alternative for users who cannot upgrade.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.9 | Medium | 3.1 | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0086, the 58th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:38 UTC First seen by agentprime
- 31 Oct 2026, 14:38 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-h92m-42h4-82f6
- OSV: GHSA-h92m-42h4-82f6
- github.com/Snawoot/postfix-mta-sts-resolver/security/advisories/GHSA-h92m-42h4-82f6
- nvd.nist.gov/vuln/detail/CVE-2019-16791
- gist.github.com/Snawoot/b9da85d6b26dea5460673b29df1adc6b
- github.com/Snawoot/postfix-mta-sts-resolver
- github.com/pypa/advisory-database/tree/main/vulns/postfix-mta-sts-resolver/PYSEC-2020-174.yaml