# CVE-2026-42167: SQL injection in ProFTPD

> Remote attackers can execute arbitrary code via SQL injection in ProFTPD when logging USER requests with specific expansions and SQL backends allowing commands.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Apr 2026
- **Updated:** 1 May 2026
- **Also known as:** DEBIAN-CVE-2026-42167, GHSA-q25r-7mmc-3mcj, OESA-2026-2158, OESA-2026-2159, OESA-2026-2760, UBUNTU-CVE-2026-42167, openSUSE-SU-2026:11352-1

## What is CVE-2026-42167?

CVE-2026-42167 is a high-severity SQL injection vulnerability in ProFTPD, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mod_sql in ProFTPD before 1.3.9a allows remote attackers to execute arbitrary code via a username, in scenarios where there is logging of USER requests with an expansion such as %U, and the SQL backend allows commands (e.g., COPY TO PROGRAM).

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `proftpd` | openSUSE:Tumbleweed | All versions | 1.3.9c-1.1 |

Products: Proftpd Proftpd.

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

Upgrade to a fixed version.

## Is CVE-2026-42167 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42167 exists.

Public exploit code:

- POCs to demonstrate CVE-2026-42167 in ProFTPD (github_poc): https://github.com/ZeroPathAI/proftpd-CVE-2026-42167-poc
- Independent reproduction, code-level root-cause analysis, and realistic-exposure write-up for CVE-2026-42167 (ProFTPD mod_sql is_escaped_text() bypass). (github_poc): https://github.com/dinosn/proftpd-CVE-2026-42167-analysis
- Python exploit for CVE-2026-42167 (ProFTPD mod_sql). Features automated file scanning and timing-based blind data exfiltration. (github_poc): https://github.com/efeanilarslan/CVE-2026-42167-Exploit
- ProFTPD SQL injection PoC (github_poc): https://github.com/jimmexploit/CVE-2026-42167-PoC
- Pre-Auth RCE in ProFTPD via mod_sql is_escaped_text() bypass (CVE-2026-42167) (github_poc): https://github.com/Sl4cK0TH/CVE-2026-42167-PoC
- https://github.com/kaleth4/CVE-2026-42167 (github_poc): https://github.com/kaleth4/CVE-2026-42167

## Other vulnerabilities in ProFTPD

- [CVE-2010-4221](https://insights.sbomify.com/CVE-2010-4221/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-20103](https://insights.sbomify.com/CVE-2010-20103/): ProFTPD 1.3.3c Backdoor Command Execution (critical 9.3)
- [CVE-2011-4130](https://insights.sbomify.com/CVE-2011-4130/): Use after free in n/a (critical 9.0)
- [CVE-2026-63090](https://insights.sbomify.com/CVE-2026-63090/): ProFTPD mod_sftp Heap Buffer Overflow via SFTP Packet Reassembly (high 8.7)
- [CVE-2026-35025](https://insights.sbomify.com/CVE-2026-35025/): ProFTPD ACL Bypass via /proc/self/root Path Prefix in RNFR (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42167 is a high-severity SQL injection vulnerability in ProFTPD, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42167 exists.

Affected product: ProFTPD. 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-42167/ (Markdown: https://insights.sbomify.com/CVE-2026-42167/index.md)
```

## Sources

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

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