Skip to content
major vulnerability· requires attention

Affects widely-used FreePBX UCP; unauthenticated access via default template credentials could lead to PBX takeovers and potential remote code execution.

Web

CVE-2026-46376

9.3
Critical
EPSS 0.43%Patch availableMay 29, 2026

Unauthenticated FreePBX UCP access via default template credentials.

common questions

Is CVE-2026-46376 being exploited?

Not confirmed. CVE-2026-46376 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.

How severe is CVE-2026-46376?

CVE-2026-46376 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46376?

Yes. A fix has been recorded for CVE-2026-46376. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46376 affect?

CVE-2026-46376 affects FreePBX UCP. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46376?

Patch to 16.0.45 or 17.0.7+ now.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
FreePBX UCP
impact

Unauthenticated UCP access may allow control of PBX settings and potential remote code execution.

action required

Immediate action required

affected versions
FreePBX security-reporting
  • affected>= 15.0.42 and < 16.0.45
  • affected>= 17.0.1 and < 17.0.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free