High Injection

CVE-2026-34185 — SQL Injection in AlanWeb SCADA

AlanWeb SCADA is vulnerable to SQL Injection across most scripts and input parameters. Because no protections are in place, an authenticated attacker can inject arbitrary SQL commands, potentially gaining full control over the database. This issue was fixed in AlanWeb SCADA version 9.8.5

Published Apr 9, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: CERT-PL

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.5% (30-day exploitation probability)+6
Technical severity (high)+6
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.47%

ahead of 39% of scored CVEs · Oct 14, 2026

Affects

Control System

AlanWeb SCADA and 1 more

CVSS base

8.8

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Control System AlanWeb SCADA, Hydrosystem.poznan Control System).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Control System	AlanWeb SCADA	< 9.8.5	Vulnerable	CVE Program (cve.org) e CISA ADP
Hydrosystem.poznan	Control System	< 9.8.5	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.7	CVSS 4.0	High	—	—	cvd@cert.pl via NIST National Vulnerability Database
8.7	CVSS 4.0	High	—	—	CERT-PL via CVE Program (cve.org) e CISA ADP
8.8	CVSS 3.1	High	2.8	5.9	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-89 · SQL Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.47%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · control system/alanweb scada
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 8.8
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Apr 9, 2026 · CERT-PL

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

cert.pl/posts/2026/04/CVE-2026-4901/
Vendor Advisory, third-party-advisory, NIST National Vulnerability Database
control-system.pl/
product, NIST National Vulnerability Database

Elsewhere on this site

Control System
every CVE for this vendor

Injection
same class

CWE-89
other pages naming this weakness

Related CVEs (same products)

Critical CVE-2026-34184 Missing Authorization inAlanWeb SCADA Apr 9, 2026
Medium CVE-2026-4901 Insertion of Sesitive Information into Log File in AlanWeb SCADA Apr 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-34185 is "SQL Injection in AlanWeb SCADA", rated High. It affects AlanWeb SCADA (Control System); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.47% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.