CVE-2026-34400
SQL Injection in Alerta Query API Allows Data Manipulation
Publication date: 2026-03-31
Last updated on: 2026-04-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| alerta_project | alerta | to 9.1.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects the Alerta monitoring tool prior to version 9.1.0. The issue is in the Query string search API (q=), which was vulnerable to SQL injection attacks. Specifically, the Postgres query parser built WHERE clauses by directly inserting user-supplied search terms into SQL strings using f-strings, allowing attackers to inject malicious SQL code.
How can this vulnerability impact me? :
The SQL injection vulnerability can allow an attacker to manipulate the database queries executed by the Alerta tool. This could lead to unauthorized data access, data modification, or even deletion. Since the vulnerability is exploitable remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the data managed by Alerta.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been patched in Alerta version 9.1.0. The immediate step to mitigate this vulnerability is to upgrade your Alerta installation to version 9.1.0 or later.