Due to a missing sanitization call in [`afsql_dd_run_query`](https://github.com/syslog-ng/syslog-ng/blob/649e6e18e3459fb…
Summary
Vulnerability reported (CVE-2026-39879). Risk of unauthorized operations or information disclosure. Exploitable via afsql_dd_run_query.
Original description
The description as published by the source.
Due to a missing sanitization call in afsql_dd_run_query, 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
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-39879 has been found.
Attackers can target a specific entry point like afsql_dd_run_query over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-39879" on the vendor's site.
CVE-2026-39879 — CWE-150 / CVSS v3 7.1
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: afsql_dd_run_query
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-150) has been reported. Attackers reach the vulnerable code path via afsql_dd_run_query without authentication.
Check the vendor advisory for the affected versions. Attack surface: afsql_dd_run_query.
Severity: High (CVSS 7.1/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-39879 syslog-ng Fixed in: 4.1.1-r1
- Ubuntu UBUNTU-CVE-2026-39879 syslog-ng