CVE-2026-39879

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
Patch available. Sources: github.
github Patch Available

Possible SQL injection in syslog-ng SQL destionation driver · Advisory · syslog-ng/syslog-ng · GitHub

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

Vendor Advisories for CVE-2026-39879(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
syslog-ng3.28.1-2 ... 4.8.1-7 (23 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
syslog-ng3.38.1-5 ... 4.8.1-7 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
syslog-ng4.8.1-5, 4.8.1-5+deb13u1, 4.8.1-6, 4.8.1-7——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
syslog-ng4.8.1-5, 4.8.1-6, 4.8.1-7——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-11 09:23 UTCEG score recompute
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 11:53 UTCEG score recompute
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 22:53 UTCEG score recompute
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 22:11 UTCEG score recompute
  11. 2026-09-05 09:29 UTCEG score recompute
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-31 04:19 UTCEG score recompute
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 02:33 UTCEG score recompute
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-28 01:55 UTCEG score recompute
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-27 00:21 UTCEG score recompute
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 22:40 UTCEG score recompute
Show 70 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 20:23 UTCEG score recompute
  3. 2026-08-23 06:07 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 04:44 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 03:22 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 01:31 UTCEG score recompute
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-19 00:09 UTCEG score recompute
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 22:40 UTCEG score recompute
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 21:19 UTCEG score recompute
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 08:38 UTCEG score recompute
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 07:17 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 05:35 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 15:33 UTCEG score recompute
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 14:07 UTCEG score recompute
  26. 2026-08-11 13:43 UTCEPSS rescore
  27. 2026-08-11 01:26 UTCEG score recompute
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-10 00:05 UTCEG score recompute
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-08 22:44 UTCEG score recompute
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-07 21:23 UTCEG score recompute
  34. 2026-08-06 20:02 UTCEG score recompute
  35. 2026-08-06 13:46 UTCEPSS rescore
  36. 2026-08-06 07:21 UTCEG score recompute
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-04 17:06 UTCEG score recompute
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:38 UTCEPSS rescore
  41. 2026-08-03 15:45 UTCEG score recompute
  42. 2026-08-03 10:36 UTCEPSS rescore
  43. 2026-08-02 14:22 UTCEG score recompute
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-01 13:00 UTCEG score recompute
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-30 22:52 UTCEG score recompute
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-30 10:11 UTCEG score recompute
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-28 20:06 UTCEG score recompute
  52. 2026-07-27 18:37 UTCEG score recompute
  53. 2026-07-27 14:13 UTCEPSS rescore
  54. 2026-07-26 17:13 UTCEG score recompute
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 04:29 UTCEG score recompute
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-25 14:18 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-24 14:17 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 03:10 UTCEG score recompute
  65. 2026-07-22 23:34 UTCEG score recompute
  66. 2026-07-22 14:08 UTCEPSS rescore
  67. 2026-07-21 15:24 UTCEPSS rescore
  68. 2026-07-20 18:41 UTCEG score recompute
  69. 2026-07-20 17:11 UTCEG score recompute
  70. 2026-07-20 17:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-39879?
CVE-2026-39879 is a high vulnerability published on July 20, 2026. Due to a missing sanitization call in afsqlddrun_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…
When was CVE-2026-39879 disclosed?
CVE-2026-39879 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39879 actively exploited?
CVE-2026-39879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.0% of all scored CVEs.
What is the CVSS score of CVE-2026-39879?
CVE-2026-39879 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-39879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39879, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39879

Explore →

Is Your Infrastructure Affected by CVE-2026-39879?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs