CVE-2022-32152: Improper TLS Certificate Validation in Splunk-to-Splunk Communications
- Vendor
- Splunk
CVE-2022-32152 is an improper certificate validation vulnerability affecting Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203. By default, affected Splunk peer-to-peer communications did not validate TLS certificates correctly, including missing hostname validation during Splunk-to-Splunk communications. As a result, connections from misconfigured nodes without valid certificates did not fail by default. Properly configured peer communications using valid certificates were not vulnerable. The issue also manifested in Splunk Python client library behavior where SSL certificate validation could be enabled without hostname verification, creating conditions for protocol impersonation and man-in-the-middle attacks.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker able to position themselves in the communication path, or otherwise exploit acceptance of invalid peer certificates, could impersonate a trusted Splunk peer and intercept or alter data exchanged between Splunk components. This can undermine the confidentiality and integrity of Splunk-to-Splunk communications and may enable unauthorized access to operational data, manipulation of telemetry or search-related traffic, and broader compromise of trust relationships within the Splunk environment. The available information indicates the primary impact is man-in-the-middle exposure rather than direct unauthenticated remote code execution.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrading is not possible, reduce exposure by enforcing proper TLS configuration for all Splunk peer communications, requiring valid certificates signed by a trusted authority, and enabling hostname validation wherever supported. Remove or replace insecure default or self-signed certificates where they are not explicitly trusted, audit peer definitions for nodes added without valid certificates, and restrict administrative access to prevent unauthorized peer enrollment. Network segmentation and protection of Splunk management and inter-node channels can further reduce man-in-the-middle risk.
Remediation
Patch, then assume compromise.
For Splunk Enterprise, upgrade to Splunk Enterprise 9.0 or later. For Splunk Cloud Platform, upgrade to version 8.2.2203 or later. After upgrading, configure TLS hostname validation for Splunk-to-Splunk communications and ensure peer communications use valid certificates. Splunk deployments should also ensure Splunk Python modules and related client components enforce certificate and hostname validation as part of TLS configuration.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2022-32152 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2022-32152 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2022-32152?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2022-32152.
- Is there a patch for CVE-2022-32152?
- For Splunk Enterprise, upgrade to Splunk Enterprise 9.0 or later. For Splunk Cloud Platform, upgrade to version 8.2.2203 or later.
- What products are affected by CVE-2022-32152?
- Splunk and Splunk Cloud Platform.
- How severe is CVE-2022-32152?
- CVE-2022-32152 has a CVSS v3.1 score of 7.2 (High) and an EPSS score of 0.84% (59th percentile) as of Oct 16, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.