● High · CVSS 8.6

How to Fix CVE-2026-26978: Deserialization RCE in security-reporting

Q: Is CVE-2026-26978 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-26978?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: Do I need to assume compromise if my security-reporting was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-20772: Critical Vulnerability in Intel(R) Connectivity Performance Suite software installers — Critical Vulnerability in Intel(R) Connectivity Performance Suite software installers
How to Fix CVE-2026-39355: CWE-862: Missing Authorization in genealogy — CWE-862: Missing Authorization in genealogy
How to Fix CVE-2026-39966: Access Control Bypass in typebot.io , Access Control Bypass in typebot.io
How to Fix CVE-2026-45252: Path Traversal in FreeBSD , Path Traversal in FreeBSD
How to Fix CVE-2026-47309: Critical Vulnerability in Escargot , Critical Vulnerability in Escargot

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 8.6 - High
Actively exploited?	Not currently listed in CISA KEV
Affected	< 16.0.71, >= 17.0.0, < 17.0.6
Fixed in	versions
Type (CWE)	CWE-502: Deserialization of Untrusted Data

What is CVE-2026-26978?

CVE-2026-26978 is an unsafe deserialization in security-reporting. The application accepts attacker-controlled serialized objects and reconstructs them without validating their type, so a crafted payload triggers code execution inside the running process. Unauthenticated remote code execution is the typical impact. Vendor description: FreePBX is an open source IP PBX. In versions below 16.0.71 and 17.0.6, the backup module does not properly sanitize data during restore operations, potentially leading to compromise if the backup contains carefully crafted hostile data.

Why this CVE matters

Deserialization bugs are a favorite of ransomware operators because they convert a single HTTP request into full code execution on the target host. Public proof-of-concept code for this CVE class typically appears within days of disclosure, and weaponized exploits follow shortly after.

For deployments of security-reporting that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

security-reporting: < 16.0.71
security-reporting: >= 17.0.0, < 17.0.6

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open security-reporting's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-26978

Read the vendor advisory in full: https://github.com/FreePBX/security-reporting/security/advisories/GHSA-5v7h-49gr-jcwr
Upgrade security-reporting to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

The commands below are runnable starting points. Adapt the package name, target version, and host paths to your environment using the vendor advisory linked under References.

npm / Yarn / pnpm


# Vendor advisory: https://github.com/FreePBX/security-reporting/security/advisories/GHSA-5v7h-49gr-jcwr
# Update to the patched release named in the advisory
npm install security-reporting@latest
# or pin to the exact fixed version from the vendor advisory
npm install security-reporting@<patched-version>
npm ls security-reporting

PyPI (pip / Poetry)


# Vendor advisory: https://github.com/FreePBX/security-reporting/security/advisories/GHSA-5v7h-49gr-jcwr
pip install --upgrade security-reporting
pip show security-reporting | grep -i version
# Poetry:
poetry add security-reporting@^<patched-version>

Docker / container


# Vendor advisory: https://github.com/FreePBX/security-reporting/security/advisories/GHSA-5v7h-49gr-jcwr
docker pull <your-registry>/security-reporting:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/security-reporting:<patched-tag>

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2026-26978 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-26978-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'security-reporting' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-26978-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'security-reporting' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2026-26978 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-26978-fix.log; }

log "Detect: current security-reporting version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' security-reporting 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' security-reporting 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-26978-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/security-reporting ] && cp -a /etc/security-reporting "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade security-reporting
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y security-reporting
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y security-reporting
fi

log "Verify: re-reading security-reporting version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' security-reporting)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' security-reporting)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: security-reporting upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

If you cannot patch immediately

Restrict access to the management interface to trusted internal IP addresses only. Block public access at the firewall and require VPN for any remote administration. Apply the patch as soon as a maintenance window allows.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-26978.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in security-reporting, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-26978 being exploited in the wild?