Skip to main content
Mallory
CriticalVulnerability

CVE-2026-49841: Pre-authentication heap buffer overflow in FreeSWITCH mod_verto

Published Jun 9, 2026 · Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS0.39%34th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freeswitch
IdentifiersCVE-2026-49841CWE-122 · Heap-based Buffer Overflow

CVE-2026-49841 is a heap-based buffer overflow in the FreeSWITCH mod_verto HTTP request handler affecting versions prior to 1.11.1. For POST requests with application/x-www-form-urlencoded bodies, the handler allocates a fixed 2 MiB buffer but accepts Content-Length values just under 10 MiB. The body-read loop uses Content-Length rather than the allocated buffer size as its bound, permitting approximately 8 MiB of attacker-controlled data to be written beyond the buffer. Request-body processing occurs before HTTP Basic authentication, making the flaw exploitable without credentials. The vulnerable handler is reachable when a verto profile has a configured vhost. The vulnerability can cause service crashes and potentially remote code execution, although code execution has not been demonstrated.

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.

An unauthenticated remote attacker can corrupt the FreeSWITCH process heap and cause crashes, disrupting affected voice services. Remote code execution is plausible but has not been demonstrated; successful code execution could compromise confidentiality and integrity within the privileges of the affected process. The vulnerability has a reported CVSS v3.1 score of 9.8.

Mitigation

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

Until patched, remove configured verto vhost entries to eliminate access to the vulnerable HTTP handler, or disable mod_verto if it is not required. Restrict the verto listener to trusted hosts and networks using firewall rules and network segmentation, and isolate the control plane from untrusted systems. HTTP Basic authentication does not prevent exploitation because the overflow occurs before authentication. TLS alone does not mitigate the flaw because request-body parsing occurs after transport termination.

Remediation

Patch, then assume compromise.

Upgrade FreeSWITCH to version 1.11.1 or a later release containing the fix.

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
FreeswitchFreeswitchapplication
FAQ

Frequently asked questions

Is CVE-2026-49841 exploited in the wild?
As of Nov 8, 2026, Mallory has no reports of CVE-2026-49841 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49841?
As of Nov 8, 2026, Mallory has found no public exploit for CVE-2026-49841.
Is there a patch for CVE-2026-49841?
Upgrade FreeSWITCH to version 1.11.1 or a later release containing the fix.
What products are affected by CVE-2026-49841?
Freeswitch.
How severe is CVE-2026-49841?
CVE-2026-49841 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.39% (34th percentile) as of Nov 8, 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.