Splunk Enterprise lacked TLS cert validation for Splunk-to-Splunk communication by default

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0097, the 62nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 15 Jun 2022. New records show when each source confirmed them.

Sources

• CVE List: CVE-2022-32152
• NVD: CVE-2022-32152

References from the CNA

• docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation confirm
• docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates confirm
• www.splunk.com/en_us/product-security/announcements/svd-2022-0602.html confirm
• research.splunk.com/application/splunk_digital_certificates_infrastructure_version/ confirm
• research.splunk.com/application/splunk_digital_certificates_lack_of_encryption/ confirm
• research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned/ confirm
• research.splunk.com/network/splunk_identified_ssl_tls_certificates/ confirm

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.