Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-45257: FreeBSD KTLS receive path arbitrary file overwrite local privilege escalation

Published Jun 26, 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.8High · v3.1
EPSS0.18%7th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-45257CWE-123 · Write-what-where Condition

CVE-2026-45257 is a local privilege escalation vulnerability in the FreeBSD kernel TLS (KTLS) receive path. The flaw exists because KTLS-RX decrypts TLS records in place, assuming the backing mbufs are anonymous and safe to modify. That assumption fails when data is placed on a socket via sendfile(2), which can use file-backed non-anonymous M_EXTPG pages or EXT_SFBUF mbufs. In the vulnerable path, when a file is sent over a loopback TCP connection without KTLS enabled on the transmit side, those file-backed mbufs can reach the receiver unchanged. The KTLS receive path then performs in-place AES-GCM decryption against memory that still references the backing file's page-cache pages, causing attacker-influenced bytes to be written directly into the page cache rather than into a private buffer. Because the attacker can choose TLS keying material and knows the original file contents, they can control the resulting plaintext bytes written into any file they can read. The overwrite bypasses normal VFS-mediated protections and can affect trusted targets such as setuid binaries.

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 an unprivileged local user to overwrite the contents of any readable file with attacker-controlled data, with the modification applied directly to the page cache and potentially written back to disk. This bypasses protections such as immutable flags including schg and can corrupt trusted executables or configuration files. In practical terms, overwriting a setuid-root binary such as /usr/bin/su can yield reliable local privilege escalation to root and potentially full system compromise. The issue also creates file integrity and persistence risk because corruption may persist on disk.

Mitigation

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

No workaround is available according to the FreeBSD advisory.

Remediation

Patch, then assume compromise.

Apply the FreeBSD vendor fix referenced in FreeBSD-SA-26:26.kTLS by upgrading to a supported corrected FreeBSD release/security branch and rebooting. The advisory states supported update paths include freebsd-update for binary distribution sets, pkg upgrade for base system packages where applicable, or applying the vendor patch at https://security.FreeBSD.org/patches/SA-26:26/ktls.patch, rebuilding the kernel, and rebooting. Fixed versions are included in FreeBSD 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16.

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-45257 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-45257 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-45257?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-45257.
Is there a patch for CVE-2026-45257?
Apply the FreeBSD vendor fix referenced in FreeBSD-SA-26:26.kTLS by upgrading to a supported corrected FreeBSD release/security branch and rebooting. The advisory states supported update paths include freebsd-update for binary distribution sets, pkg upgrade for base system packages where applicable, or applying the vendor patch at https://security.FreeBSD.org/patches/SA-26:26/ktls.patch, rebuilding the kernel, and rebooting.
What products are affected by CVE-2026-45257?
Freebsd.
How severe is CVE-2026-45257?
CVE-2026-45257 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.18% (7th 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 activity21Community discussion across Reddit, Mastodon, and other social sources.