Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
3.7

Docker Druid images risk log leaks via email

published 9 days ago
Summary

The Log4j component used in several Docker Druid images does not properly check the server's certificate when sending logs by email, so an attacker could intercept the connection and read the log messages. This could expose sensitive information contained in those logs. Update the images to versions that include Log4j 2.12.3 or later, or apply the Log4j patch yourself, and ensure that only trusted email servers are used.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Debian:13 docker hardened images druid-36-fips All versions
Docker Hardened Images:Debian:13 docker hardened images druid-36 All versions
Docker Hardened Images:Debian:13 docker hardened images druid-37-fips All versions
Docker Hardened Images:Debian:13 docker hardened images druid-37 All versions
Docker Hardened Images:Debian:13 docker hardened images druid-38-fips All versions
Docker Hardened Images:Debian:13 docker hardened images druid-38 All versions
Original advisory text
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS…
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1
References
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
3.7 Low
Timeline
Published10 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta