Cyber Resilience

CVE-2026-49472

Freeswitch ≤ 1.11.0

Published
09 June 2026
Modified
17 June 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0022 13th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2026-49472 is a medium-severity Improper Encoding or Escaping of Output (CWE-116) vulnerability in Freeswitch Freeswitch. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-49841Same product: Freeswitch Freeswitch
CVE-2023-40018Same product: Freeswitch Freeswitch
CVE-2023-51443Same product: Freeswitch Freeswitch
CVE-2026-49475Same product: Freeswitch Freeswitch
CVE-2026-49840Same product: Freeswitch Freeswitch
CVE-2026-49843Same product: Freeswitch Freeswitch
CVE-2026-49848Same product: Freeswitch Freeswitch
CVE-2026-49847Same product: Freeswitch Freeswitch
CVE-2023-40019Same product: Freeswitch Freeswitch
CVE-2026-49842Same product: Freeswitch Freeswitch

Affected Assets

freeswitch
freeswitch
≤ 1.11.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.2.1
  • V1.2.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-116

Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper output encoding to prevent injection and message malformation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.

finds

Security testing can detect missing or incorrect encoding but does not itself implement the control.

prevents

Secure development life cycle mandates output encoding/escaping practices that directly prevent improper encoding.

prevents

Application security requirements include explicit rules for safe output handling and encoding.

prevents

Secure architecture principles reduce the likelihood of missing encoding but do not prescribe the actual technique.

References