Skip to main content
Mallory
CriticalVulnerability

CVE-2022-32151: Improper Certificate Validation in Splunk Enterprise and Splunk Cloud Platform Python HTTP Libraries

Published Jun 15, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.1Critical · v3.1
EPSS0.81%58th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Splunk
IdentifiersCVE-2022-32151CWE-295 · Improper Certificate Validation

CVE-2022-32151 is an improper certificate validation vulnerability in Splunk Enterprise before version 9.0 and Splunk Cloud Platform before version 8.2.2203. The Python httplib and urllib libraries shipped with these products did not validate TLS certificates against certificate authority trust stores by default. As a result, outbound or inter-component HTTPS connections made through these libraries could accept untrusted or spoofed server certificates. Python 3 client libraries were later changed to verify server certificates by default and to use the appropriate CA certificate stores for each library. Applications and add-ons that bundle and use their own HTTP libraries are not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Successful exploitation can allow a man-in-the-middle or protocol impersonation attack against affected Splunk communications that rely on the vulnerable Python libraries. An attacker positioned on the network path, or otherwise able to present a spoofed endpoint, could intercept and manipulate data transmitted over supposedly protected channels, undermining confidentiality and integrity. In Splunk deployments, this could expose sensitive operational data and may enable unauthorized actions in affected communication flows.

Mitigation

If you can’t patch tonight, do this now.

Where immediate upgrade is not possible, reduce exposure by enforcing strict TLS certificate validation and host name validation for Splunk-to-Splunk communications, ensuring trusted CA stores are correctly configured, and limiting opportunities for network-path interception. Review Splunk configurations related to server certificate verification and TLS validation behavior to ensure certificate checks are not disabled.

Remediation

Patch, then assume compromise.

For Splunk Enterprise, upgrade to version 9.0 or later and enable TLS host name validation for Splunk-to-Splunk communications. For Splunk Cloud Platform, use version 8.2.2203 or later. The remediation also includes the change in Python 3 client library behavior so that server certificates are verified by default against appropriate CA certificate stores.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
SplunkSplunkapplication
SplunkSplunk Cloud Platformapplication
FAQ

Frequently asked questions

Is CVE-2022-32151 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-32151 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-32151?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2022-32151.
Is there a patch for CVE-2022-32151?
For Splunk Enterprise, upgrade to version 9.0 or later and enable TLS host name validation for Splunk-to-Splunk communications. For Splunk Cloud Platform, use version 8.2.2203 or later.
What products are affected by CVE-2022-32151?
Splunk and Splunk Cloud Platform.
How severe is CVE-2022-32151?
CVE-2022-32151 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.81% (58th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.