Ansible does not verify that the server hostname matches a domain name in certificates

published 2015-08-12 11 y ago modified 2026-06-17 4 mo ago also GHSA-w64c-pxjj-h866 , PYSEC-2015-1 , EUVD-2015-0001

cvss: 7.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

Ansible before 1.9.2 does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

Patch / fix

fixed in 1 distros 3

pypi ansible 1.9.2

debian ubuntu opensuse

ansible Debian 14, Debian 13, Debian 12 1.9.2+dfsg-1

debian advisories DEBIAN-CVE-2015-3908

ansible Ubuntu Pro 14.04 LTS 1.5.4+dfsg-1ubuntu0.1~esm3

ubuntu advisories UBUNTU-CVE-2015-3908

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

ansible-14 openSUSE Tumbleweed 14.6.0-1.1
ansible-13 openSUSE Tumbleweed 13.7.0-1.1
ansible-12 openSUSE Tumbleweed 12.2.0-1.1
ansible-11 openSUSE Tumbleweed 11.11.0-1.1
ansible-10 openSUSE Tumbleweed 10.6.0-1.1
ansible-9 openSUSE Tumbleweed 9.8.0-1.1
ansible openSUSE Tumbleweed 2.2.0.0-1.1

opensuse advisories openSUSE-SU-2026:12447-1 openSUSE-SU-2026:10944-1 openSUSE-SU-2025:15753-1 openSUSE-SU-2025:15605-1 openSUSE-SU-2024:14536-1 openSUSE-SU-2024:14244-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-3908 updated 2026-06-27 cvss 7.6

ansible: multiple issues fixed in 1.9.2

Red Hat OpenShift Enterprise 3 ansible Red Hat OpenStack Platform 10 (Newton) ansible Red Hat Quickstart Cloud Installer 1 ansible Red Hat Storage 3 ansible Red Hat Storage Console 2 ansible
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	ansible	<1.9.2	1.9.2

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

lists.opensuse.org /opensuse-updates/2015-07/msg00051.html
vendor-advisory, web, third-party-advisory
lists.opensuse.org /opensuse-updates/2015-08/msg00029.html
vendor-advisory, web, third-party-advisory
ansible.com /security
web, vendor-advisory
openwall.com /lists/oss-security/2015/07/14/4
mailing-list, web
lists.debian.org /debian-lts-announce/2019/09/msg00016.html
mailing-list, web
nvd.nist.gov /vuln/detail/CVE-2015-3908
advisory
github.com /advisories/GHSA-w64c-pxjj-h866
advisory
github.com /ansible/ansible
package
github.com /pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2015-1.yaml
web

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.

Summary