Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-49413: FreeBSD Linuxulator AT_SECURE Privilege Escalation

Published Jun 27, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.1High · v3.1
EPSS0.13%2nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-49413CWE-269

CVE-2026-49413 is a local privilege-escalation vulnerability in the FreeBSD Linuxulator. When executing set-user-ID or set-group-ID Linux binaries under emulation, the Linuxulator determined whether the process was running in a privileged setugid context by checking the P_SUGID process flag. During execve(2), that flag had not yet been set at the point where the auxiliary vector was constructed, causing AT_SECURE to be incorrectly set to 0 for privileged Linux executables. As a result, the runtime linker did not enter secure-execution mode and unsafe environment-controlled behavior remained enabled. An unprivileged local user could therefore supply LD_PRELOAD to force loading of an attacker-controlled shared library into a set-user-ID or set-group-ID Linux binary and execute code with the privileges of that binary.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows local privilege escalation from an unprivileged account to the effective privileges of the targeted set-user-ID or set-group-ID Linux binary executed through the Linuxulator. Where such a binary runs with elevated privileges, this can result in compromise of the affected account and potentially full root access. The flaw undermines the expected secure-execution protections for privileged Linux binaries on FreeBSD systems using Linux emulation.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available. Exposure is absent if the Linuxulator kernel modules are not loaded, or if the system does not contain or execute Linux binaries with set-user-ID or set-group-ID permissions. Reducing attack surface therefore consists of disabling Linux emulation where unnecessary and removing or avoiding privileged Linux executables under emulation until patched.

Remediation

Patch, then assume compromise.

Update FreeBSD to a corrected supported version or branch containing the Linuxulator fix and reboot the system. Reported fixed versions and branches include 15.1-STABLE after 2026-06-09T19:17:33Z, 15.1-RC3-p1 after 2026-06-09T19:20:11Z, 15.0-RELEASE-p10 after 2026-06-09T19:19:48Z, 14.4-STABLE after 2026-06-09T19:17:50Z, 14.4-RELEASE-p6 after 2026-06-09T19:19:11Z, and 14.3-RELEASE-p15 after 2026-06-09T19:18:40Z. Apply the vendor-provided base system update or patch and reboot to ensure the corrected execve and auxiliary-vector handling is active.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-49413Repository contains a single C proof-of-concept exploit (exploit.c) plus a minimal README image. The exploit is a local privilege escalation tool targeting FreeBSD systems running the Linux compatibility layer ('Linuxulator'). Its workflow is structured in three phases: (1) environment validation, where it checks for loaded linux/linux64 kernel modules, verifies the presence of the Linux dynamic loader under /compat/linux/, and searches a hardcoded list of candidate Linux binaries for a setuid-root target; (2) vulnerability verification, where it executes the chosen target with LD_SHOW_AUXV=1 and parses output for AT_SECURE to determine whether the runtime incorrectly leaves AT_SECURE=0; and (3) exploitation, where it writes a malicious shared-library source file to /tmp/.poc_evil.c, compiles it into /tmp/.poc_evil.so using cc -shared -fPIC -nostdlib, brands it as a Linux ELF with brandelf, sets LD_PRELOAD to that library, and execs the target binary. The embedded payload is a constructor function that runs before the target program, checks whether effective UID is 0, then sets real/effective IDs to 0 and execves /bin/sh, yielding a root shell. No network communication or remote C2 is present; all observables are local filesystem paths and kernel module names. This is a real exploit PoC rather than a detector-only script, and it is operational because it includes a working privilege-escalation payload with limited hardcoded targeting.ii4gsp · Disclosed Jun 10, 2026 · c · markdown · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-49413 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49413 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49413?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-49413, the earliest disclosed Jun 10, 2026.
Is there a patch for CVE-2026-49413?
Update FreeBSD to a corrected supported version or branch containing the Linuxulator fix and reboot the system. Reported fixed versions and branches include 15.1-STABLE after 2026-06-09T19:17:33Z, 15.1-RC3-p1 after 2026-06-09T19:20:11Z, 15.0-RELEASE-p10 after 2026-06-09T19:19:48Z, 14.4-STABLE after 2026-06-09T19:17:50Z, 14.4-RELEASE-p6 after 2026-06-09T19:19:11Z, and 14.3-RELEASE-p15 after 2026-06-09T19:18:40Z.
What products are affected by CVE-2026-49413?
Freebsd.
How severe is CVE-2026-49413?
CVE-2026-49413 has a CVSS v3.1 score of 7.1 (High) and an EPSS score of 0.13% (2nd percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.