How severe is CVE-2026-46376?

CVE-2026-46376 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-46376 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-46376?

CVE-2026-46376 affects Sangoma Freepbx. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-46376?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-46376 have an EU (EUVD) identifier?

Yes. CVE-2026-46376 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-33295.

When was CVE-2026-46376 published?

CVE-2026-46376 was published on 2026-05-29 and last updated on 2026-06-17.

CVE-2026-46376

CVE-2026-46376 is a critical-severity vulnerability in Sangoma Freepbx with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-798.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v4: 9.3
EPSS exploit prediction: 0% (34th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-33295
Weakness: CWE-798
Affected product: Sangoma Freepbx
Published: 2026-05-29
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-46376?: 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.
How severe is CVE-2026-46376?: CVE-2026-46376 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-46376 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-46376?: CVE-2026-46376 affects Sangoma Freepbx. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-46376?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-46376 have an EU (EUVD) identifier?: Yes. CVE-2026-46376 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-33295.
When was CVE-2026-46376 published?: CVE-2026-46376 was published on 2026-05-29 and last updated on 2026-06-17.

References

https://github.com/FreePBX/security-reporting/security/advisories/GHSA-m55x-h47x-v3gx

Affected products (1)

cpe:2.3:a:sangoma:freepbx:*:*:*:*:*:*:*:*

More vulnerabilities in Sangoma Freepbx

CVE-2014-7235 — Critical (CVSS 10.0): htdocs_ari/includes/login.php in the ARI Framework module/Asterisk Recording Interface (ARI) in FreePBX before 2.9.0.9,…
CVE-2025-66039 — Critical (CVSS 9.8): FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions are vulnerable to…
CVE-2025-57819 — Critical (CVSS 9.8): FreePBX is an open-source web-based graphical user interface. FreePBX 15, 16, and 17 endpoints are vulnerable due to…
CVE-2019-19006 — Critical (CVSS 9.8): Sangoma FreePBX 115.0.16.26 and below, 14.0.13.11 and below, 13.0.197.13 and below have Incorrect Access Control.
CVE-2026-44239 — High (CVSS 8.8): FreePBX is an open source IP PBX. Prior to 16.0.22 and 17.0.5, the Dashboard module's getcontent AJAX handler includes…
CVE-2026-44238 — High (CVSS 8.8): FreePBX is an open source IP PBX. Prior to 16.0.50 and 17.0.11, the CDR Reports module page allows SQL injection…

All CVEs affecting Sangoma Freepbx →

Other CWE-798 (Use of Hard-coded Credentials) vulnerabilities

CVE-2026-13768 — Critical (CVSS 10.0): Gardyn devices expose a privileged iothubowner key. Access to this key will allow a malicious user to invoke an IoTHub…
CVE-2026-45631 — Critical (CVSS 10.0): Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.27.0 to before 0.29.3, a hardcoded…
CVE-2026-22769 — Critical (CVSS 10.0): Dell RecoverPoint for Virtual Machines, versions prior to 6.0.3.1 HF1, contain a hardcoded credential vulnerability.…
CVE-2025-42890 — Critical (CVSS 10.0): SQL Anywhere Monitor (Non-GUI) baked credentials into the code,exposing the resources or functionality to unintended…
CVE-2025-7503 — Critical (CVSS 10.0): An OEM IP camera manufactured by Shenzhen Liandian Communication Technology LTD exposes a Telnet service (port 23) with…
CVE-2025-20309 — Critical (CVSS 10.0): A vulnerability in Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session…

Browse all CWE-798 (Use of Hard-coded Credentials) vulnerabilities →