splunk-sdk does not properly verify untrusted TLS server certificates

published 2019-03-19 7y ago modified 2026-06-17 4mo ago also GHSA-f58w-649r-qjr9 , PYSEC-2019-203 , EUVD-2019-0131

cvss: 8.1; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

Splunk-SDK-Python before 1.6.6 does not properly verify untrusted TLS server certificates, which could result in man-in-the-middle attacks.

Patch / fix

fixed in 2

pypi splunk-sdk 1.6.6
splunk software_development_kit 1.6.6

Is CVE-2019-5729 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.1	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.0	8.1	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	splunk-sdk	<1.6.6	1.6.6

Classification

Weakness

CWE-295 Improper Certificate Validation

References

splunk.com /view/SP-CAAAQAD
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2019-5729
advisory
github.com /advisories/GHSA-f58w-649r-qjr9
advisory
github.com /pypa/advisory-database/tree/main/vulns/splunk-sdk/PYSEC-2019-203.yaml
web
github.com /splunk/splunk-sdk-python
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.