Skip to content
Applications

CVE-2026-73661

8.6
High
EPSS 0.34%Patch availableAug 14, 2026

Backup restore can disable FreePBX auth (AUTHTYPE=none), enabling authentication bypass.

common questions

Is CVE-2026-73661 being exploited?

Not confirmed. CVE-2026-73661 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.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-73661?

CVE-2026-73661 is rated High with a CVSS score of 8.6. 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-73661?

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

What does CVE-2026-73661 affect?

CVE-2026-73661 affects FreePBX Framework <16.0.47, FreePBX Framework <17.0.30, FreePBX instances allowing backup restore or writable backup files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73661?

Upgrade Framework to 16.0.47/17.0.30; restrict backup file write/restore privileges and audit restores.

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

executive summary
technical analysis
affected
FreePBX Framework <16.0.47FreePBX Framework <17.0.30FreePBX instances allowing backup restore or writable backup files
impact

Authenticated user with backup-restore or write access can set AUTHTYPE=none to disable authentication and gain admin access to FreePBX UI.

action required

Immediate action required

affected versions
FreePBX framework
  • affected< 16.0.47
  • affected>= 17.0.1 and < 17.0.30

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