SQL Injection in alerta-server (CVE-2026-34400)
Summary
SQL injection in alerta-server (CVE-2026-34400). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 9.1.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-34400 has been found in alerta-server.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade alerta-server to 9.1.0 or later.
If unsure, ask your IT team or search "alerta-server CVE-2026-34400" on the vendor's site.
CVE-2026-34400 (alerta-server) — CWE-89 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 9.1.0 — apply immediately
Workaround: Upgrade to v9.1.0 or later.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in alerta-server.
Check the vendor advisory for the affected versions of alerta-server.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 9.1.0.
Workaround: Upgrade to v9.1.0 or later.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'alerta-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'alerta-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
alerta-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Upgrade to v9.1.0 or later.パッチが適用されるまでの応急処置として、Upgrade to v9.1.0 or later. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade alerta-server to 9.1.0ステージング環境で 9.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com