Skip to main content
Mallory
CriticalVulnerability

CVE-2026-49840: FreeSWITCH libesl esl_recv_event() Content-Length integer handling flaw

Published Jun 9, 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.
CVSS9.1Critical · v3.1
EPSS0.31%24th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freeswitch
IdentifiersCVE-2026-49840CWE-190

CVE-2026-49840 affects FreeSWITCH libesl prior to version 1.11.1. In esl_recv_event(), the library parses the Content-Length header using atol() and passes the resulting value directly to malloc(len + 1) without validating sign or magnitude. A malicious or man-in-the-middle ESL peer can supply a negative Content-Length value, causing incorrect allocation behavior and subsequent heap corruption or process crash during event frame handling. The issue is reachable before client authentication to the peer and impacts processes linked against libesl, including fs_cli, mod_esl, mod_hash, and other ESL-based tools.

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 corrupt heap memory or crash the affected process. The provided context specifically states that negative Content-Length values can trigger memory corruption, including cases such as copying attacker-controlled data into an invalid or zero-byte allocation, and lower negative values may cause NULL pointer dereference. The article also notes potential remote code execution, but the supplied vulnerability description specifically confirms heap corruption and denial of service; code execution is possible but not established in the provided source.

Mitigation

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

Until patching is completed, restrict ESL connectivity to trusted networks and trusted peers only. Prevent exposure of the ESL/control-plane network to untrusted hosts, and limit which hosts ESL clients are allowed to connect to. Because the issue can be triggered by a malicious or man-in-the-middle peer before authentication, network isolation and peer trust enforcement are the primary mitigations.

Remediation

Patch, then assume compromise.

Upgrade FreeSWITCH to version 1.11.1 or later, which patches the vulnerable libesl handling in esl_recv_event(). Any application or component linked against vulnerable libesl should be updated to the fixed release.

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-49840 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49840 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49840?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49840.
Is there a patch for CVE-2026-49840?
Upgrade FreeSWITCH to version 1.11.1 or later, which patches the vulnerable libesl handling in esl_recv_event(). Any application or component linked against vulnerable libesl should be updated to the fixed release.
What products are affected by CVE-2026-49840?
Freeswitch.
How severe is CVE-2026-49840?
CVE-2026-49840 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.31% (24th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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

View more in app →
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 activity1Community discussion across Reddit, Mastodon, and other social sources.