FreeSWITCH mod_sofia: stack buffer overflow from an over-long SIP Contact display-name
- Exploited
- No known exploitation
- Fix
- Fixed in 1.11.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.11.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
FreeSWITCH's mod_sofia module contains a stack buffer overflow, affecting versions from 1.10.0 through 1.11.1, that is triggered by an over-long SIP Contact display name during dialog-event subscriptions. An attacker can reach it remotely over the network with low-privilege login credentials, and the flaw can crash the FreeSWITCH process and all active calls; it only applies when presence management is enabled, directly or through shared appearance.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
FreeSWITCH is an open-source software telecommunications platform. From 1.10.0 to 1.11.1, there is a stack-based buffer overflow in mod_sofia when processing SIP Contact display names for dialog-event notifications. A peer can establish a dialog containing an excessively long display name and subsequently subscribe to that entity’s dialog events, causing the stored value to overflow a fixed 512-byte stack buffer. Exploitation requires presence management to be enabled, directly or through shared appearance, and normally requires valid profile credentials unless subscription authentication is disabled. The overflow can terminate the FreeSWITCH process and all active calls. This vulnerability is fixed in version 1.11.2.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.11.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- signalwire freeswitch
fixed in 1.11.2
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116572
Is CVE-2026-116572 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-116572?
freeswitch: before 1.11.2.Source: cve.now feed data
How do I fix CVE-2026-116572?
Upgrade to a fixed version: 1.11.2.Source: cve.now feed data