Skip to main content
Mallory
HighVulnerability

CVE-2026-49416: Integer Overflow in FreeBSD vt(4) CONS_HISTORY ioctl

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.8High · v3.1
EPSS0.15%5th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-49416CWE-190 · Integer Overflow or Wraparound

CVE-2026-49416 is a local kernel vulnerability in the FreeBSD vt(4) console subsystem's CONS_HISTORY ioctl handler. The handler did not adequately validate the requested history size. Supplying a sufficiently large history size causes an integer overflow during buffer size calculation, leading to a heap allocation that is smaller than intended. Subsequent initialization of the history buffer then writes past the end of the allocated heap region, resulting in a kernel heap out-of-bounds write. The issue is reachable by an unprivileged local user who has access to a vt(4) device.

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 with access to a vt(4) device to corrupt kernel heap memory via an out-of-bounds write. This can potentially be leveraged for local privilege escalation to root. Kernel memory corruption may also cause instability or crashes, although the advisory specifically highlights possible privilege escalation.

Mitigation

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

No workaround is available.

Remediation

Patch, then assume compromise.

Upgrade FreeBSD to a supported fixed version on a stable or release/security branch after the vendor correction dates. The advisory identifies fixes in FreeBSD 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16. For affected systems, apply updates via pkg upgrade where supported for 15.0-RELEASE base-package installations, use freebsd-update for RELEASE systems installed from binary distribution sets, or apply the vendor patch from https://security.FreeBSD.org/patches/SA-26:34/vt.patch, then rebuild and reboot.

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-49416 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49416 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49416?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49416.
Is there a patch for CVE-2026-49416?
Upgrade FreeBSD to a supported fixed version on a stable or release/security branch after the vendor correction dates. The advisory identifies fixes in FreeBSD 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16.
What products are affected by CVE-2026-49416?
Freebsd.
How severe is CVE-2026-49416?
CVE-2026-49416 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.15% (5th 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.