Vulnerability in Sangoma Freepbx (CVE-2026-46376)
Summary
Vulnerability in Sangoma Freepbx (CVE-2026-46376). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 16.0.45 or later.
Original description
The description as published by the source.
FreePBX is an open source IP PBX. From 15.0.42 to before 16.0.45 and 17.0.7, unauthenticated users may be able to access the User Control Panel (UCP) using hard-coded initial template credentials if these were not immediately changed by the Administrator who enabled UCP. Authenticated access to ACP is required for the initial setup of UCP generic templates, but after that, without further steps by the admin, unauthenticated users may be able to gain access. This vulnerability is fixed in 16.0.45 and 17.0.7.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46376 has been found in Sangoma Freepbx.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade Sangoma Freepbx to 16.0.45 or later.
If unsure, ask your IT team or search "Sangoma Freepbx CVE-2026-46376" on the vendor's site.
CVE-2026-46376 (Sangoma Freepbx) — CWE-798 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 16.0.45 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-798) exists in Sangoma Freepbx.
Check the vendor advisory for the affected versions of Sangoma Freepbx.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 16.0.45.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Freepbx' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Freepbx' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Freepbxを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Sangoma Freepbx to 16.0.45ステージング環境で 16.0.45 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。