# CVE-2026-126617: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in hMailServer

> Remote attackers can alter SQL statements in hMailServer's database layer, injecting SQL that runs with the server's database privileges; hMailServer operators should care.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-g98g-j6w4-w22m

## What is CVE-2026-126617?

CVE-2026-126617 is a high-severity SQL injection vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection in the database layer of Progressive Robot hMailServer 6.0.0-B1 through 6.2.18, when the server uses MySQL/MariaDB or PostgreSQL, allows a remote attacker to alter SQL statements the server runs. On those two engines parameters are not bound: SQLStatement::GenerateFromCommand wrote each value into the statement's text as a quoted literal with a separate string replacement over the whole text per parameter, so a value holding the name of a parameter substituted after it had that name replaced, inside the value, by the later value with its own quotes, which ended the literal early and placed the later value in the statement as SQL. The row the server writes for each recipient of a queued message carries the recipient's address twice, so in the default configuration an authenticated user who may send mail reaches it by sending to an address of their choosing. A remote unauthenticated sender reaches the same statement through a message the server sends to the envelope sender, such as a delivery failure notice or an automatic reply, and, when greylisting or message indexing is enabled (both are off by default), through the greylisting record's envelope addresses or through the message metadata the server stores for IMAP SORT, which carries four header fields of a received message. An altered statement runs with the privileges of the server's database account; on PostgreSQL, whose client call runs every statement in the text it is given, further statements can follow it, while on MySQL/MariaDB, where one statement is run per call, the change is confined to the statement it is in. SQL Server and SQL Server Compact, where parameters are bound, are not affected.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-126617?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-126617?

No fix has been published for CVE-2026-126617 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126617 being exploited?

There is no known exploitation of CVE-2026-126617 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126617 and fix it if it is affected.

What it is: CVE-2026-126617 is a high-severity SQL injection vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126617 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Progressive Robot Ltd hMailServer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126617/ (Markdown: https://insights.sbomify.com/CVE-2026-126617/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126617
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126617
- OSV: https://osv.dev/vulnerability/CVE-2026-126617

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126617/
Summaries are generated and may contain mistakes; the official description above is the record.
