Emergency server help: get in touch

FreePBX Security Updates, August to September 2026: What to Update and How to Check

The 17 FreePBX security advisories of August and September 2026, the module versions that fix them, a read-only check script and how to update safely.

Published Updated 8 min read

Short answer: FreePBX security updates fixed 17 advisories published between 21 August and 29 September 2026, in the framework, backup, ucp, sangomartapi (Sangoma Connect), recordings, cel, recording_report, sipstation, contactmanager and pinsets modules. On FreePBX 17 you are covered when framework is at least 17.0.33, backup 17.0.13, sangomartapi 17.0.29 and ucp 17.0.10 (full list below). Check with fwconsole ma list or our read-only script, update with fwconsole ma upgradeall, then fwconsole reload. Asterisk itself had no new advisories in this period. (Reviewed October 2026.)

Most of these advisories need a logged-in user, but several only need a UCP (user portal) account, one needs nothing more than an incoming call, and the most serious one needs no login at all. We took the list from the official FreePBX security advisories on GitHub, checked each fixed version there, and tested a version-check script on our FreePBX 17 lab.

The advisories and the fixed versions

Dates are the GitHub publication dates; severity is the CVSS v4 score shown on each advisory. None of them had a CVE ID or an entry in CISA’s Known Exploited Vulnerabilities list when we checked on 21 October 2026, and no advisory says it was exploited in the wild.

PublishedAdvisoryModuleFixed (17)Fixed (16)SeverityWho can use it
21 AugGHSA-h9vq-j62m-6m73sangomartapi17.0.2616.0.55Critical 9.3No login: SQL injection in the Sangoma Connect RT API login (remote code execution)
21 AugGHSA-rgq3-mgw4-rcfhucp17.0.1016.0.41High 8.8No login: missing authorization lets anyone reset or overwrite users’ UCP data
24 AugGHSA-2f5p-xvrc-j2wfsangomartapi17.0.2616.0.55High 8.7Logged in: remote code execution via FindMeFollowMe in Sangoma Connect
24 AugGHSA-pw3c-6wm2-mxg4framework17.0.3116.0.48High 8.6Admin with limited rights can escalate privileges
24 AugGHSA-rvwr-xrpc-4hf4backup17.0.1216.0.74High 8.6Logged in: backup metadata hooks execution bypass
24 AugGHSA-65g4-v227-g8m3backup17.0.1216.0.74High 8.6Logged in: command injection via restore file name
31 AugGHSA-m8mc-g8fg-4765framework17.0.3216.0.49High 8.6Broken access control in the GraphQL API
17 SepGHSA-3hr3-9whj-655fframework17.0.3316.0.50High 8.7Any UCP user: remote code execution via AMI
17 SepGHSA-fwpm-x5rh-2pr6backup17.0.1316.0.75High 8.7Logged in: code execution via unsafe unserialize in restore
17 SepGHSA-5457-hm39-pcfcbackup17.0.1316.0.76High 8.6Admin: root command injection in GraphQL restoreBackup
17 SepGHSA-9cjf-xw9x-55hhrecordings17.0.616.0.21High 8.6Admin: command execution via dialplan injection
17 SepGHSA-hq6g-xv43-3v87cel17.0.316.0.21High 8.7No login: caller ID of an incoming call becomes stored XSS in CEL Reports
17 SepGHSA-x6qq-4527-j9gfrecording_report17.0.3.1616.0.33.8Medium 6.9Admin can read any file via the call recording report
29 SepGHSA-3827-8r8q-362jsangomartapi17.0.2916.0.57High 7.1Any UCP user can read the whole database (SQL injection)
29 SepGHSA-pq27-pw7r-4x8jsipstation17.0.4–High 8.6Admin: SQL injection via SIPSTATION
29 SepGHSA-7wg2-66mh-g7mgpinsets17.0.416.0.9High 8.6Logged in: privilege escalation via SQL injection in Pinsets
29 SepGHSA-j82w-j6cr-56m6contactmanager17.0.816.0.29Medium 5.3UCP user can change other users’ contacts

For each module, the highest version in the table is the one that covers all of its advisories. On FreePBX 17 that is:

ModuleMinimum version on FreePBX 17
framework17.0.33
backup17.0.13
sangomartapi17.0.29
ucp17.0.10
recordings17.0.6
cel17.0.3
recording_report17.0.3.16
sipstation17.0.4
contactmanager17.0.8
pinsets17.0.4

On FreePBX 16, use the “Fixed (16)” column, taking the highest value per module (for example backup 16.0.76 and framework 16.0.50). FreePBX 16 still received fixes for these, but plan the move: see upgrading FreePBX 16 to 17.

Check your PBX

fwconsole ma list shows every installed module with its version and status. To compare the ten modules above in one go, this read-only script prints each one with the fixed version. It exits 0 when everything is covered, 1 if anything needs an update, and 3 if it could not tell (fwconsole failed, the module list could not be read, or a version did not look like a FreePBX 17 version), so a monitoring check never treats a read problem as “OK”:

#!/bin/bash
# fpbx-advisory-check.sh - FreePBX 17: compare installed module versions with the
# fixed versions from the advisories of 21 Aug - 29 Sep 2026. Read-only. Run as root.
# Exit: 0 all OK, 1 at least one update needed, 3 something could not be checked.
set -u
FIXED="framework 17.0.33
backup 17.0.13
recordings 17.0.6
cel 17.0.3
recording_report 17.0.3.16
sangomartapi 17.0.29
sipstation 17.0.4
contactmanager 17.0.8
pinsets 17.0.4
ucp 17.0.10"
list=$(fwconsole ma list 2>/dev/null) || { echo "UNKNOWN: fwconsole ma list failed (run as root on FreePBX 17)"; exit 3; }
# Rows look like: | framework | 17.0.33.2 | Enabled | GPLv2+ | ...
rows=$(printf '%s\n' "$list" | awk -F'|' 'NF>=4 {m=$2; v=$3; gsub(/ /,"",m); gsub(/ /,"",v); if (m!="" && m!="Module") print}')
if [ "$(printf '%s\n' "$rows" | grep -c 'framework')" -ne 1 ]; then
  echo "UNKNOWN: could not read the module list (framework not found); check: fwconsole ma list"; exit 3
fi
need=0; unknown=0
printf '%-18s %-12s %-12s %s\n' MODULE INSTALLED FIXED_IN STATUS
while read -r mod fix; do
  info=$(printf '%s\n' "$rows" | awk -F'|' -v m="$mod" '{a=$2; gsub(/ /,"",a)} a==m {v=$3; t=$4; gsub(/ /,"",v); gsub(/^ +| +$/,"",t); print v "|" t; exit}')
  if [ -z "$info" ]; then printf '%-18s %-12s %-12s %s\n' "$mod" "-" "$fix" "not installed"; continue; fi
  ver=${info%%|*}; st=${info#*|}
  if ! [[ "$ver" =~ ^17\.[0-9]+(\.[0-9]+)*$ ]]; then
    s="UNKNOWN (version '$ver' is not a FreePBX 17 version)"; unknown=1
  elif [ "$(printf '%s\n%s\n' "$fix" "$ver" | sort -V | head -1)" = "$fix" ]; then s="OK"
  else s="UPDATE NEEDED"; need=1; fi
  [ "$st" != "Enabled" ] && s="$s (${st:-status unknown})"
  printf '%-18s %-12s %-12s %s\n' "$mod" "$ver" "$fix" "$s"
done <<< "$FIXED"
[ "$need" = 1 ] && exit 1
[ "$unknown" = 1 ] && exit 3
exit 0

On our lab (FreePBX 17.0.33.2, modules updated on 17 October) every installed module reported OK; sangomartapi, sipstation and recording_report were not installed. To test the other branch we fed it a module list with older versions: framework 17.0.32.9, backup 17.0.12 and pinsets 17.0.3.1 came back as UPDATE NEEDED, a disabled module was flagged, and the exit code was 1. On 21 October we also fed it a version of 17.0.x, a FreePBX 16 version, an empty version, an empty list, a list without the usual table layout and a failing fwconsole: each was reported as UNKNOWN with exit code 3, except that an update needed elsewhere in the list still gave exit code 1. A disabled module that is still installed should be updated too, or removed.

Also check for anything else waiting: fwconsole ma showupgrades printed “Up to date.” on our lab.

Install the FreePBX security updates

Take a backup first (see FreePBX backup and restore from the command line), then update the modules and apply the configuration. These are the commands from Sangoma’s fwconsole documentation:

fwconsole ma refreshsignatures
fwconsole ma upgradeall          # or: fwconsole ma upgrade framework backup ucp ...
fwconsole reload
fwconsole chown
bash fpbx-advisory-check.sh; echo "exit $?"

Run it in a quiet period and keep the backup at hand until calls, UCP and the admin GUI are checked.

Reduce the exposure while you update

  • Sangoma Connect RT API (sangomartapi). The critical advisory is reachable without a login. If you do not use Sangoma Connect, remove the module; if you do, update it and make sure its service is not open to the internet. The advisory names port 6082; check with ss -ltnp | grep 6082.
  • UCP. Three advisories need only a UCP login, and one more needs no login at all. Keep UCP behind a VPN; if it has to be reachable from outside, update first and follow FreePBX UCP from outside the office (HTTPS only, admin GUI private, firewall allow-list where possible, fail2ban with your own addresses excluded). See also FreePBX firewall and intrusion detection.
  • CEL Reports. The caller ID XSS fires when an admin opens CEL Reports, so a call from anyone is enough to plant it. Update cel before opening that report.
  • Admin accounts. Several fixes are for logged-in admins. Keep admin access on the LAN or VPN and remove unused admin users.

Asterisk in the same period

Asterisk published no new security advisories between the June batch and 21 October 2026. The last security releases were 20.20.1, 21.12.3, 22.10.1 and 23.4.1 on 25 June 2026; the August releases 20.21.0, 22.11.0 and 23.5.0 list no security advisories in their changelogs. Check your version with asterisk -rx "core show version" (our lab: 22.11.0) and compare it with our software versions tracker.

How we checked

  • Advisory data: the FreePBX/security-reporting repository on GitHub, read through the GitHub API on 21 October 2026 (published date, severity, affected and patched versions for each module). Asterisk advisories: the asterisk/asterisk repository the same way.
  • Script: tested on our lab (FreePBX 17.0.33.2, Asterisk 22.11.0, Debian 12) against the real module list, and against substituted module lists with older versions, malformed versions, an empty list and a failing fwconsole to test the “update needed” and “unknown” paths and their exit codes.
  • Not tested: exploiting any of the issues, FreePBX 16, and the module upgrade from an affected version (our lab was already current).

FAQ

Which FreePBX advisory from 2026 is the most serious?

GHSA-h9vq-j62m-6m73 (21 August, CVSS 9.3): an unauthenticated SQL injection in the Sangoma Connect RT API login that leads to remote code execution. It is fixed in sangomartapi 17.0.26 and 16.0.55; later advisories raise that module to 17.0.29 and 16.0.57.

Is my FreePBX affected if UCP is not exposed to the internet?

Yes, update anyway. Hiding UCP removes the outside route to the UCP advisories, but three of them only need a UCP account, so any internal user with one can still use them; the ucp issue needs no login from anyone who can reach UCP; and the sangomartapi and CEL issues do not depend on UCP at all (the CEL one only needs an incoming call).

Do I need to update Asterisk for these?

No. All of these are FreePBX module fixes. Asterisk had no new security advisories in this period.

How do I check FreePBX module versions from the command line?

fwconsole ma list lists every module with its version and status; fwconsole ma showupgrades lists available updates.

At a glance

FreePBX Security Updates, August to September 2026: What to Update and How to Check summary card: FreePBX published 17 security advisories between 21 August and 29 September 2026, in the framework, backup, ucp, sangoma…
In short: FreePBX published 17 security advisories between 21 August and 29 September 2026, in the framework, backup, ucp, sangomartapi (Sangoma Connect), recordings, cel, recording_report, sipstation…

Share this guide

Free website test

Is your website set up right?

Check SSL, security headers, redirects, robots.txt, sitemap, llms.txt and security.txt in one test. It takes about 30 seconds.