# CVE-2026-39879: SQL injection in syslog-ng SQL destionation driver

> Attackers can inject SQL commands via untrusted sources in syslog-ng's SQL destination driver, requiring manual configuration to exploit.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** BELL-CVE-2026-39879, DEBIAN-CVE-2026-39879, GHSA-qwf9-6222-m24m, UBUNTU-CVE-2026-39879

## What is CVE-2026-39879?

CVE-2026-39879 is a high-severity SQL injection vulnerability in syslog-ng, published on 20 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Due to a missing sanitization call in [`afsql_dd_run_query`](https://github.com/syslog-ng/syslog-ng/blob/649e6e18e3459fb4467000a88dfb12fa97f9719c/modules/afsql/afsql.c#L219), syslog-ng before 4.12 are vulnerable to SQL injection from an untrusted source. This is not part of the default configuration, the SQL driver has to be manually configured.

Fixes are in syslog-ng 4.12, syslog-ng Premium Edition 8.2 and syslog-ng Store Box 7.8

Weakness: CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences)

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


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

Upgrade to a fixed version.

## Is CVE-2026-39879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39879 is a high-severity SQL injection vulnerability in syslog-ng, published on 20 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39879 in the wild and no public exploit code.

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

## Sources

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

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