dbcve.org
FreeBSDOperating system

CVE-2026-49414

HIGH · 7.8 CVSS v3.1 Published 2026-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ELF image activator in the kernel clears per-process ASLR preference flags for setuid binaries after computing the PIE base address rather than before. This timing flaw allows an unprivileged local user to disable ASLR for setuid PIE binaries by calling procctl(2) before execve(2), leaving the user-requested ASLR disable in effect when the base address is chosen and significantly easing exploitation of memory corruption vulnerabilities.

MitigationThe fix requires kernel-level changes to clear ASLR preference flags before computing the PIE base address. Until patched, avoid relying solely on ASLR to protect setuid binaries and ensure those binaries are free from memory corruption flaws.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreeBSDOperating system
Affected:= 14.3= 14.4= 15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FreeBSD version
    Run `uname -r` or `freebsd-version -k` to get the installed kernel version
    Affected if The version is 14.3, 14.4, or 15.0 (exact matches)
  2. Identify setuid PIE binaries
    Use `find / -perm -4000 -type f` to locate setuid binaries, then check if any are PIE (Position Independent Executable) using `readelf -d <binary> | grep DYNAMIC` or examine the binary with `file` command
    Affected if Any setuid binaries exist that are compiled as PIE executables on an affected FreeBSD version
  3. Verify procctl(2) ASLR control exists
    Check if procctl(2) system call with PIE base control is available: review procctl(2) man page or test the system call wrapper
    Affected if The system supports procctl(2) ASLR control on setuid binaries on an affected version
  4. Check kernel source patch status
    Inspect the kernel source file responsible for ELF image activation (typically in sys/kern/imgact_elf.c) and look for the presence or absence of the ASLR flag clearing logic before PIE base computation
    Affected if The kernel source shows ASLR preference flags are cleared after PIE base computation rather than before, and the system runs an unpatched affected version

The environment is affected if running FreeBSD 14.3, 14.4, or 15.0 with setuid PIE binaries present and the kernel lacks the fix that clears ASLR preference flags before computing the PIE base address.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The fix requires kernel-level changes to clear ASLR preference flags before computing the PIE base address. Until patched, avoid relying solely on ASLR to protect setuid binaries and ensure those binaries are free from memory corruption flaws.

Recommended fix Moderate confidence

FreeBSD 15.1 or later (or latest 14.x stable branch such as 14.5+)

  1. Upgrade the FreeBSD system to a version where the vulnerability is patched. For FreeBSD 14.x systems, upgrade to the latest stable 14.x release (14.5 or later if available). For FreeBSD 15.0 systems, upgrade to FreeBSD 15.1 or later.
  2. After upgrade, verify the running kernel version with: uname -r
  3. Confirm the fix is applied by checking the FreeBSD security advisory at security.freebsd.org for CVE-2026-49414
Caveat Standard minor version upgrade risks apply - review FreeBSD release notes for any configuration or compatibility changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in FreeBSD Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49414 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data