Vulnerability in Sangoma Freepbx (CVE-2026-44237)
Summary
Vulnerability in Sangoma Freepbx (CVE-2026-44237). Confidential information can be exposed externally. Mitigation: upgrade to 17.0.8 or later.
Original description
The description as published by the source.
FreePBX is an open source IP PBX. Prior to 17.0.8, the FreePBX api module's OAuth2 implementation does not sufficiently validate client credentials during token issuance. Knowledge of a valid client_id is required. The validateClient() method in ClientRepository.php unconditionally returns true, allowing any party with knowledge of a valid client_id to obtain OAuth2 access tokens without providing the correct client_secret. This vulnerability is fixed in 17.0.8.
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-44237 has been found in Sangoma Freepbx.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade Sangoma Freepbx to 17.0.8 or later.
If unsure, ask your IT team or search "Sangoma Freepbx CVE-2026-44237" on the vendor's site.
CVE-2026-44237 (Sangoma Freepbx) — CWE-1390 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 17.0.8 — 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-1390) exists in Sangoma Freepbx.
Check the vendor advisory for the affected versions of Sangoma Freepbx.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 17.0.8.
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 17.0.8ステージング環境で 17.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。