Improper certificate validation in Elasticsearch
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-295.
Summary
In Logstash versions after 6.4.0 and before 6.8.15 and 7.12.0 a TLS certificate validation flaw was found in the monitoring feature. When specifying a trusted server CA certificate Logstash would not properly verify the certificate returned by the monitoring server. This could result in a man in the middle style attack against the Logstash monitoring data.
Why it matters now
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-2021-22138
- 2026-10-03 Alias added: GHSA-56cm-rmmq-hqpv
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-2021-22138 · CVE Program
- CVE-2021-22138 · NVD
- FIRST EPSS
- GHSA-56cm-rmmq-hqpv · 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