dbcve.org
FreeswitchApplication

CVE-2026-49472

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 1.11.0 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to version 1.11.0, FreeSWITCH includes a vulnerable function, PREFIX(prologTok)(), in libs/xmlrpc-c/lib/expat/xmltok/xmltok_impl.c, which was cloned from an outdated and vulnerable version in libexpat/libexpat. The function did not receive the corresponding security patch. This issue has been patched in version 1.11.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FreeSWITCH versions prior to 1.11.0 contain a vulnerable cloned function PREFIX(prologTok)() in the xmlrpc-c libexpat XML tokenizer implementation. This function was copied from an outdated libexpat version and did not receive corresponding security patches, likely exposing XML parsing vulnerabilities such as buffer overflows or XXE issues.

MitigationUpgrade FreeSWITCH to version 1.11.0 or later to incorporate the patched xmltok_impl.c file.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreeswitchApplication
Affected:< 1.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify FreeSWITCH installation
    Run 'freeswitch -version' or check for freeswitch binaries in /usr/local/freeswitch/bin/, /opt/freeswitch/bin/, or similar common paths
    Affected if FreeSWITCH is not found or not accessible
  2. Determine installed FreeSWITCH version
    Execute 'freeswitch -version' and capture the output which displays the version number (e.g., 1.10.x, 1.8.x)
    Affected if Version displayed is lower than 1.11.0 (e.g., 1.10.10, 1.8.9, etc.)
  3. Confirm the vulnerable expat library is present
    Search for the xmltok_impl.c file in libs/xmlrpc-c/lib/expat within the FreeSWITCH source or installation directories
    Affected if The file exists and the FreeSWITCH version is below 1.11.0
  4. Cross-check with system package manager
    If installed via package manager (apt, yum, dnf), run 'rpm -qa | grep freeswitch' or 'dpkg -l | grep freeswitch' to verify the installed package version
    Affected if Package version listed is below 1.11.0

You are affected if FreeSWITCH is installed and its version is less than 1.11.0, indicating the vulnerable cloned expat XML parser code is present in the libs/xmlrpc-c/lib/expat directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.11.0 or later
Fixed in 1.11.0
Interim mitigation

Upgrade FreeSWITCH to version 1.11.0 or later to incorporate the patched xmltok_impl.c file.

Recommended fix High confidence

FreeSWITCH 1.11.0

  1. 1. Backup the current FreeSWITCH configuration directory (typically /etc/freeswitch or /usr/local/freeswitch/conf)
  2. 2. Backup any custom modules, scripts, or dialplans
  3. 3. Stop the FreeSWITCH service
  4. 4. Upgrade FreeSWITCH to version 1.11.0 or later using the appropriate package manager or source compilation for your OS
  5. 5. Restore the backed-up configuration files
  6. 6. Verify the XML parser library version in libs/xmlrpc-c/lib/expat/xmltok/xmltok_impl.c is patched (the PREFIX(prologTok) function should have the security fix)
  7. 7. Start the FreeSWITCH service
  8. 8. Test critical call flows and IVR paths to ensure functionality
Caveat Upgrading from pre-1.11.0 versions may introduce breaking changes in configuration syntax, module loading, or API behavior - review the 1.11.0 release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freeswitch Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49472 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data