CVE-2026-49414
Freebsd 14.3 … 15.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-49414 is a high-severity Incorrect Behavior Order: Early Validation (CWE-179) vulnerability in Freebsd Freebsd. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 1th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-39966
Vulnerability Data
The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the…
more
base address was chosen. An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.3.8V2.2.1V3.7.2
Mitigating Controls (NIST 800-53 r5) AI
Requiring validation of information inputs after canonicalization or sanitization directly stops the incorrect ordering that lets modified dangerous data bypass checks.
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.
CWE-179 is a coding flaw enabling input-validation bypasses; it neither impairs post-incident forensic/root-cause processes (RS.AN-03) nor is itself mitigated or exposed by those processes.
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.
Security testing can detect early-validation flaws but does not inherently prevent them in design.
Secure development life cycle mandates validation after canonicalization or sanitization, directly preventing early-validation bypasses.
Application security requirements include input validation rules that must be applied after protective transformations.
Secure architecture principles discourage unsafe ordering of validation and sanitization steps.
Secure coding standards explicitly require canonicalization before validation to avoid CWE-179.