Read the docs
TI-2019-12568 Aliases CVE-2019-16791GHSA-h92m-42h4-82f6

downgrade of effective Strict Transport Security (STS) policy in postfix-mta-sts-resolver

Priority LOW 32CWE-757Published · Updated

Key facts

Attack vector
Local
Privileges required
High
User interaction
Required
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.

Summary

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.

Why it matters now

EPSS 0.00858 58th percentileScored 2026-11-07
Fix Fixed postfix-mta-sts-resolver (Snawoot): 0.5.1postfix-mta-sts-resolver (PyPI): 0.5.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Snawootpostfix-mta-sts-resolverbefore 0.5.10.5.1Patch availableCNA
—postfix-mta-sts-resolver (PyPI)before 0.5.10.5.1Patch availableGHSA-h92m-42h4-82f6
  • postfix-mta-sts-resolver VendorSnawoot Affected before 0.5.1 Fixed in 0.5.1 Patch available CNA
  • postfix-mta-sts-resolver (PyPI) Vendor— Affected before 0.5.1 Fixed in 0.5.1 Patch available GHSA-h92m-42h4-82f6

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:postfix-mta-sts-resolver_project:postfix-mta-sts-resolver:*:*:*:*:*:*:*:*before 0.5.1VulnerablePostfix-mta-sts-resolver Project

Remediation

  • Fix · CNA postfix-mta-sts-resolver (Snawoot) Fixed in 0.5.1
  • Fix · GHSA-h92m-42h4-82f6 postfix-mta-sts-resolver (PyPI) Fixed in 0.5.1 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2019-16791
  2. 2026-10-03 Alias added: GHSA-h92m-42h4-82f6

References

Patch 2

Advisory 1

Other 2

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences