● Medium · CVSS 6.9

How to Fix CVE-2026-34400: alerta-server has potential SQL Injection vulnerability in Query String Syntax (q=) API

Q: Is CVE-2026-34400 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-34400?

CVSS rates it 6.9 (Medium). Use that score to set your patch priority alongside the other items in your queue.

Q: Do I have to take alerta offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-34400 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

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

How to Fix CVE-2026-8621: Authentication Bypass in crabbox — Authentication Bypass in crabbox
How to Fix CVE-2026-37540: n/a in n/a — n/a in n/a
How to Fix CVE-2026-7266: SQL Injection in Pizzafy Ecommerce System , SQL Injection in Pizzafy Ecommerce System
How to Fix CVE-2026-25757: Critical Vulnerability in spree , Critical Vulnerability in spree
How to Fix CVE-2026-40344: CWE-287: Improper Authentication in minio , CWE-287: Improper Authentication in minio

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance


Severity	CVSS 6.9, Medium
Actively exploited?	No
Affected	alerta (< 9.1.0)
Fixed in	9.1.0
Type (CWE)	CWE-89: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVE-2026-34400 is a alerta-server has potential sql injection vulnerability in query string syntax (q=) api in alerta. The fix is to upgrade to 9.1.0 and apply the runnable commands below.

What is CVE-2026-34400?

Alerta is a monitoring tool. Prior to version 9.1.0, the Query string search API (q=) was vulnerable to SQL injection via the Postgres query parser, which built WHERE clauses by interpolating user-supplied search terms directly into SQL strings via f-strings. This issue has been patched in version 9.1.0.

In practical terms, a successful attacker gets SQL injection that can read or modify the backing database. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You are affected if you run alerta at a version listed in the Affected row above. Probe your installed build with the commands below.


# Confirm the installed version via your package manager
dpkg -l | grep -i alerta   # Debian/Ubuntu
rpm -qa | grep -i alerta   # RHEL/CentOS/Rocky

How to fix CVE-2026-34400

The primary fix is to upgrade to the patched build listed in the Fixed in row above (9.1.0). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


sudo apt-get update
sudo apt-get install --only-upgrade alerta
# Confirm the installed version meets or exceeds 9.1.0
dpkg -s alerta | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security alerta -y
rpm -q alerta

Windows (PowerShell, admin)


winget upgrade --id 'Alerta.alerta' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\alerta-9.1.0.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows): detect, back up, upgrade, verify, log


# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\alerta-Patch-CVE-2026-34400.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-34400 remediation for Alerta alerta"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*alerta*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'9.1.0') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\alerta-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Alerta\alerta"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer
$installer = "$env:TEMP\alerta-9.1.0.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*alerta*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'9.1.0') {
    Write-Log "SUCCESS: now at $verify (>= 9.1.0)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux): detect, back up, upgrade, verify, log


#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/alerta-patch-cve-2026-34400.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-34400 remediation for Alerta alerta"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s alerta >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' alerta)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q alerta >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' alerta)
    PKG_MGR=dnf
else
    log "alerta not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: alerta=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/alerta-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/alerta /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y alerta
else
    sudo dnf upgrade --security -y alerta
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' alerta)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' alerta)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against 9.1.0 and restart the affected service if needed."

If you cannot patch immediately

These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.

Block obvious SQL injection patterns with a WAF rule


# ModSecurity / OWASP CRS-style rule
SecRule ARGS "@rx (?i)(union(.|\n)+?select|select(.|\n)+?from|insert(.|\n)+?into)" \
  "id:900100,phase:2,deny,log,msg:'SQLi pattern blocked'"

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


dpkg -l | grep -i "alerta"   # Debian/Ubuntu
rpm -qa | grep -i "alerta"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed 9.1.0.

Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-34400 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-34400 being actively exploited?