CVE-2020-14365: Ansible Engine - GPG Signature Bypass

ansible Updated 02 Oct 2025

Summary

23/09/2020

Disclosed on

CVE-2020-14365

CVE

Yes i

Fix available

Moderate

Severity

7.1

CVSS Score

CVE-2020-14365: A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. Affects ansible across 2 version ranges.

>= 2.8.0, < 2.8.16rc1 >= 2.9.0, < 2.9.14rc1

Fixed in 2.8.16rc1 or 2.9.14rc1, depending on the release line you run. How to fix ↓

Also tracked for

ansible · Alpine:v3.10

The same CVE-2020-14365 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

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

Ansible Engine is an open-source automation platform that allows users to automate IT tasks such as configuration management, application deployment, and orchestration. It provides a simple and powerful way to automate complex tasks across a wide range of systems. The Ansible Engine package is available on PyPI (Python Package Index) and is widely used by developers and system administrators.

Vulnerability Detail

A vulnerability was discovered in Ansible Engine versions 2.8.x before 2.8.15 and 2.9.x before 2.9.13. The issue occurs when installing packages using the dnf module. By default, GPG signatures are ignored during installation, even when the 'disable_gpg_check' option is set to False. This flaw allows malicious packages to be installed on the system, potentially leading to arbitrary code execution through package installation scripts. The primary impact of this vulnerability is on the integrity and availability of the system.

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 versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

>= 2.8.0, < 2.8.16rc1 2.8.16rc1

pip install --upgrade "ansible==2.8.16rc1"

>= 2.9.0, < 2.9.14rc1 2.9.14rc1

pip install --upgrade "ansible==2.9.14rc1"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, users can manually verify the GPG signatures of packages before installation. This can be done by retrieving the GPG key used to sign the package and verifying it against the package's signature. Here is an example of how to manually verify a package using GPG:

Retrieve the GPG key used to sign the package.
Import the GPG key into the local keyring.
Download the package and its signature.
Verify the package's signature using the imported GPG key.
Install the package only if the signature is valid.

Please note that this workaround requires manual intervention and may not be feasible for large-scale deployments.

Conclusion

In conclusion, the Ansible Engine vulnerability (CVE-2020-14365) allows for the bypassing of GPG signatures during package installation, potentially leading to the installation of malicious packages and arbitrary code execution. It is crucial to upgrade to the fixed versions of Ansible Engine (2.8.16rc1 or later for 2.8.x, and 2.9.14rc1 or later for 2.9.x) to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ansible →

FAQ

What is Ansible Engine?

Ansible Engine is an open-source automation platform used for configuration management, application deployment, and orchestration.

What versions of Ansible Engine are affected by this vulnerability?

Versions 2.8.x before 2.8.15 and 2.9.x before 2.9.13 of Ansible Engine are affected.

What is the impact of this vulnerability?

This vulnerability allows malicious packages to be installed on the system, potentially leading to arbitrary code execution.

Is there a fix available for this vulnerability?

Yes, fixed versions of Ansible Engine are available. Upgrade to version 2.8.16rc1 or later for 2.8.x versions, and version 2.9.14rc1 or later for 2.9.x versions.

Are there any workarounds for this vulnerability?

A temporary workaround is to manually verify the GPG signatures of packages before installation. However, this may not be feasible for large-scale deployments.

References

Related vulnerabilities

Recent vulnerabilities recorded for ansible.

View all ansible vulnerabilities →