CVE-2015-3908: Ansible SSL Server Spoofing Vulnerability

ansible Updated 02 Oct 2025

Summary

12/08/2015
Yes i
High
7.5

CVE-2015-3908: 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 SS... Affects ansible versions < 1.9.2. Fixed in 1.9.2. How to fix ↓

Also tracked for

The same CVE-2015-3908 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Ansible is an open-source automation tool that allows users to automate IT tasks such as configuration management, application deployment, and orchestration. It is widely used for managing infrastructure and automating workflows. This vulnerability affects Ansible versions prior to 1.9.2. Ansible uses SSL/TLS to secure communication between the control node and managed hosts. However, it fails to verify that the server hostname matches the domain name in the X.509 certificate, making it susceptible to man-in-the-middle attacks.

Vulnerability Detail

The vulnerability (CVE-2015-3908) in Ansible allows an attacker to spoof SSL servers by presenting an arbitrary valid certificate. This means that an attacker can intercept and modify communication between the control node and managed hosts without being detected. By impersonating a legitimate SSL server, the attacker can potentially gain unauthorized access to sensitive information, manipulate data, or perform other malicious actions.

How To Fix

Latest published version: 14.5.0 as of 22 Oct 2026

pip install --upgrade "ansible==14.5.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.9.2

This is the first release that contains the fix.

pip install --upgrade "ansible==1.9.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring that they only communicate with trusted Ansible servers and by regularly monitoring network traffic for any suspicious activity.

Conclusion

The Ansible SSL Server Spoofing vulnerability (CVE-2015-3908) allows attackers to impersonate SSL servers and intercept communication between the control node and managed hosts. To mitigate this risk, it is crucial to upgrade Ansible to version 1.9.2 or later. Regularly monitoring network traffic and ensuring communication with trusted Ansible servers can also help reduce the impact of this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ansible →

Share this vulnerability

FAQ

The vulnerability allows an attacker to impersonate an SSL server and intercept communication between the control node and managed hosts. This can lead to unauthorized access, data manipulation, and other malicious activities.

If you are using Ansible version prior to 1.9.2, your installation is vulnerable to this SSL server spoofing vulnerability. It is recommended to upgrade to the latest version to mitigate the risk.

There are no publicly known exploits for this vulnerability at the time of writing. However, it is important to apply the recommended fix to prevent potential attacks.

While it is technically possible to manually verify the server hostname against the X.509 certificate, it is highly recommended to upgrade to the fixed version of Ansible. Manual verification may introduce human error and is not a reliable long-term solution.

You can find more information about this vulnerability in the official advisory published by the Ansible project. Additionally, you can refer to the CVE identifier (CVE-2015-3908) for further details.

Related vulnerabilities

Recent vulnerabilities recorded for ansible.

How To Fix

Latest published version: 14.5.0 as of 22 Oct 2026

pip install --upgrade "ansible==14.5.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.9.2

This is the first release that contains the fix.

pip install --upgrade "ansible==1.9.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback