Skip to main content
Mallory
HighVulnerability

CVE-2026-49421: FreeBSD unlinkat/funlinkat AT_RESOLVE_BENEATH Path Resolution Restriction Bypass

Published Aug 19, 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%3rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-49421CWE-693

CVE-2026-49421 is a FreeBSD kernel pathname resolution protection bypass affecting unlinkat(2) and funlinkat(2). The implementation validated the AT_RESOLVE_BENEATH flag but failed to propagate that flag to the underlying path lookup logic. As a result, although callers could request path resolution constrained beneath a starting directory, the restriction was silently not enforced during resolution. This allows path traversal above the intended directory tree during unlink operations, defeating the expected containment semantics of AT_RESOLVE_BENEATH for these system calls.

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.

A process or application that relies on AT_RESOLVE_BENEATH with unlinkat(2) or funlinkat(2) to confine deletions to a specific directory subtree may be induced to resolve paths outside that subtree and delete files outside the intended directory tree. The primary impact is unauthorized file deletion and bypass of pathname containment protections, which may undermine sandboxing or other security boundaries built on these semantics.

Mitigation

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

No workaround is available according to the FreeBSD advisory. Exposure is limited to applications that use AT_RESOLVE_BENEATH with unlinkat(2) or funlinkat(2); applications not relying on those flags for path containment are not affected.

Remediation

Patch, then assume compromise.

Upgrade FreeBSD to a supported stable or release/security branch containing the fix. FreeBSD states fixes are available in 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16. Apply updates via freebsd-update or pkg upgrade where applicable, or apply the vendor source patch and recompile the kernel, then reboot into the corrected kernel.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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-49421 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49421 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49421?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49421.
Is there a patch for CVE-2026-49421?
Upgrade FreeBSD to a supported stable or release/security branch containing the fix. FreeBSD states fixes are available in 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16.
What products are affected by CVE-2026-49421?
Freebsd.
How severe is CVE-2026-49421?
CVE-2026-49421 has a CVSS v3.1 score of 7.1 (High) and an EPSS score of 0.13% (3rd 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 activity1Community discussion across Reddit, Mastodon, and other social sources.