Cyber Resilience

CVE-2026-43964

Postfix ≤ 3.8.16

Published
04 May 2026
Modified
07 August 2026
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0049 40th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2026-43964 is a low-severity Off-by-one Error (CWE-193) vulnerability in Postfix Postfix. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Postfix before 3.8.16, 3.9 before 3.9.10, and 3.10 before 3.10.9 sometimes allows a buffer over-read and process crash via an enhanced status code that lacks text after the third number.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-51764Same product: Postfix Postfix
CVE-2026-35541Same product class: email / collaboration
CVE-2026-55005Same product class: email / collaboration
CVE-2025-59032Same product class: email / collaboration
CVE-2018-0986Same product class: email / collaboration
CVE-2019-11500Same product class: email / collaboration
CVE-2017-8540Same product class: email / collaboration
CVE-2025-59248Same product class: email / collaboration
CVE-2025-64666Same product class: email / collaboration
CVE-2026-33369Same product class: email / collaboration

Affected Assets

postfix
postfix
≤ 3.8.16 · 3.9.0 — 3.9.10 · 3.10.0 — 3.10.9

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.2.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover off-by-one errors in loops, bounds, and calculations before deployment.

Requiring documented development standards and tools can embed bounds-checking and arithmetic-correctness rules that stop off-by-one mistakes at introduction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent off-by-one errors via reviews, static analysis, and testing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect off-by-one errors before release.

prevents

Secure development life cycle includes requirements and reviews that can catch off-by-one errors.

prevents

Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.

prevents

Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.

prevents

Secure coding directly addresses off-by-one errors through coding standards and peer review.

References