# CVE-2022-32156: Splunk Enterprise and Universal Forwarder CLI connections lacked TLS cert validation

Status: published. Published: 2022-06-14. Updated: 2026-11-02.

In Splunk Enterprise and Universal Forwarder versions before 9.0, the Splunk command-line interface (CLI) did not validate TLS certificates while connecting to a remote Splunk platform instance by default. After updating to version 9.0, see  Configure TLS host name validation for the Splunk CLI https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI  to enable the remediation. The vulnerability does not affect the Splunk Cloud Platform. At the time of publishing, we have no evidence of exploitation of this vulnerability by external parties.

The issue requires conditions beyond the control of a potential bad actor such as a machine-in-the-middle attack. Hence, Splunk rates the complexity of the attack as High.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Splunk / Splunk Enterprise: ≥ 0; < 9.0.0 (affected, custom). Source: CNA: Splunk
- Splunk / Universal Forwarder: ≥ 0; < 9.0.0 (affected, custom). Source: CNA: Splunk

## NVD configuration conditions

Affected CPE matches depend on the following AND/OR and negation conditions:

```json
[
  {
    "negate": false,
    "nodes": [
      {
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
            "versionEndExcluding": "9.0",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:a:splunk:universal_forwarder:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "9.0",
            "vulnerable": true
          }
        ],
        "negate": false,
        "operator": "OR"
      }
    ],
    "operator": "OR"
  }
]
```

## Severity and prioritization

- CVSS 3.1: 7.4 (high); CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N; source: CNA: Splunk

- CVSS 3.1: 8.1 (high); CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H; source: CNA: Splunk

- CVSS 3.1: 8.1 (high); CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H; source: NVD: nvd@nist.gov

- CVSS 3.1: 8.1 (high); CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H; source: NVD: prodsec@splunk.com

- CVSS 2.0: 6.8 (medium); AV:N/AC:M/Au:N/C:P/I:P/A:P; source: NVD: nvd@nist.gov

- CISA KEV: No listing in collected sources

- EPSS: 0.82% as of 2026-11-02; percentile 57.31%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-295

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html (CNA: Splunk)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates (CNA: Splunk)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI (CNA: Splunk)

- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html (ADP: CVE; x_transferred)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates (ADP: CVE; x_transferred)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI (ADP: CVE; x_transferred)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI (prodsec@splunk.com; Mitigation, Vendor Advisory)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates (prodsec@splunk.com; Release Notes, Vendor Advisory)

- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html (prodsec@splunk.com; Vendor Advisory)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation#Configure_TLS_host_name_validation_for_the_Splunk_CLI (af854a3a-2127-422b-91ae-364da2661108; Mitigation, Vendor Advisory)

- https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates (af854a3a-2127-422b-91ae-364da2661108; Release Notes, Vendor Advisory)

- https://www.splunk.com/en_us/product-security/announcements/svd-2022-0606.html (af854a3a-2127-422b-91ae-364da2661108; Vendor Advisory)

## Provenance

- CNA: Splunk: https://www.cve.org/CVERecord?id=CVE-2022-32156; retrieved 2026-11-02; source updated 2026-11-02

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32156; retrieved 2026-11-03; source updated 2026-11-02

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2022-32156; retrieved 2026-11-02; source updated Not reported

Revision: 0a32c83c553ed1800a52217e80ccc5392210dca60d8e4d3088a262103886b50d

Canonical: https://y2.dev/cve/CVE-2022-32156

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.