Skip to main content
Mallory
HighVulnerability

CVE-2026-49420: Stack-based buffer overflow in FreeBSD libalias RTSP handler

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.
CVSS8.8High · v3.1
EPSS0.42%37th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-49420CWE-121 · Stack-based Buffer Overflow

CVE-2026-49420 is a stack-based buffer overflow in the RTSP handler of FreeBSD's libalias network address translation library. The flaw arises because the handler rewrites outgoing RTSP packets into a fixed-length stack buffer without verifying that the rewritten data fits within that buffer, and without ensuring that the rewritten result fits back into the original packet. When attacker-controlled RTSP traffic is processed through libalias in NAT configurations, this unsafe rewrite logic can corrupt stack memory. The vulnerable functionality is exposed through FreeBSD NAT components that use libalias for RTSP-aware aliasing, including ipfw NAT and natd.

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 can cause a stack buffer overflow leading to denial of service and potentially remote code execution. In configurations using ipfw NAT, exploitation may achieve code execution in kernel context. In configurations using natd, exploitation may achieve code execution in the natd process, which generally runs with root privileges. As a result, the vulnerability can lead to full compromise of the affected system, including loss of confidentiality, integrity, and availability.

Mitigation

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

If RTSP NAT handling is not required, disable the vulnerable RTSP helper. On natd deployments, remove the RTSP helper library from the libalias configuration and restart natd so the vulnerable code is not loaded. On ipfw NAT deployments, avoid loading the RTSP helper kernel module unless explicitly needed. As an additional workaround, filter NAT-processed RTSP-related traffic before it reaches the NAT rule, including traffic associated with standard RTSP ports such as 554 and 7070.

Remediation

Patch, then assume compromise.

Update FreeBSD to a fixed supported release level. Reported fixed versions include 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16. Where normal base-system update mechanisms are applicable, install the vendor-provided security updates and reboot. If updating through source or patch workflows, apply the vendor patch for the affected branch, rebuild the affected components as required, and reboot the system.

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-49420 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49420 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49420?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49420.
Is there a patch for CVE-2026-49420?
Update FreeBSD to a fixed supported release level. Reported fixed versions include 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16.
What products are affected by CVE-2026-49420?
Freebsd.
How severe is CVE-2026-49420?
CVE-2026-49420 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.42% (37th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity3Community discussion across Reddit, Mastodon, and other social sources.