Sensitive information in log files in Elastic Logstash
Priority LOW 31CWE-532Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-532.
Summary
When logging warnings regarding deprecated settings, Logstash before 5.6.6 and 6.x before 6.1.2 could inadvertently log sensitive information.
Why it matters now
EPSS 0.01017 63rd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2018-3817
- 2026-10-03 Alias added: GHSA-m5wv-852x-cj2g
References
More Elastic Logstash vulnerabilities
- TI-2019-05366 Information disclosure through error messages in Elastic Logstash CVSS 3.1CRITICAL 9.8
- TI-2026-25862 Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write CVSS 3.1CRITICAL 9.8
- TI-2014-03539 Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to… CVSS 2.0HIGH 7.5
- TI-2015-04531 Logstash 1.5.x before 1.5.3 and 1.4.x before 1.4.4 allows remote attackers to read… CVSS 3.0HIGH 7.5
- TI-2019-05374 Uncontrolled resource consumption in Elastic Logstash CVSS 3.1HIGH 7.5
- TI-2023-25173 Logstash Insertion of Sensitive Information into Log File CVSS 3.1HIGH 8.4
Sources
- CVE-2018-3817 · CVE Program
- CVE-2018-3817 · NVD
- FIRST EPSS
- GHSA-m5wv-852x-cj2g · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences