# CVE-2020-14365: Improper Verification of Cryptographic Signature in ansible

Source: https://junglewise.ai/threats/cve-2020-14365-improper-verification-of-cryptographic-signature-in-ansible  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2020-09-23  
License: CC BY 4.0 with a link back

CVE-2020-14365 · Severity: low · CVSS 3.1 · Published 2020-09-23

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. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.

Technologies: [ansible (PyPI)](https://junglewise.ai/threats/technologies/ansible). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2020-14365 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2020-14365 being exploited in the wild.

**How severe is CVE-2020-14365?** Low severity, with a CVSS score of 3.1, published 23 September 2020.

**Which products and versions are affected?** ansible (PyPI) ECOSYSTEM:introduced=2.8.0,fixed=2.8.16rc1,introduced=2.9.0,fixed=2.9.14rc1, ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.15.

**Is there a fix for CVE-2020-14365?** Yes. ansible (PyPI): upgrade to 2.8.15, 2.9.14rc1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2020-14365?** Check whether you run ansible (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- ansible (PyPI): upgrade to 2.8.15, 2.9.14rc1 or later

  ```sh
  pip install "ansible>=2.9.14rc1"
  ```


## Affected products

- ansible (PyPI) ECOSYSTEM:introduced=2.8.0,fixed=2.8.16rc1,introduced=2.9.0,fixed=2.9.14rc1, ECOSYSTEM:introduced=2.8.0a1,fixed=2.8.15

## Identifiers

- CVE-2020-14365
- GHSA-m429-fhmv-c6q2
- PYSEC-2020-209

## Related threats

- [PYSEC-2026-1120 - Ansible symlink attack vulnerability](https://junglewise.ai/threats/cve-2023-5115-ansible-symlink-attack-vulnerability)
- [PYSEC-2026-768 - Ansible leaks password to logs](https://junglewise.ai/threats/cve-2022-3697-ansible-leaks-password-to-logs)
- [PYSEC-2026-618 - Insertion of Sensitive Information into Log File in ansible](https://junglewise.ai/threats/cve-2021-20180-insertion-of-sensitive-information-into-log-file-in-ansible)
- [Ansible community.general information exposure in Keycloak user module](https://junglewise.ai/threats/cve-2025-14010-ansible-community-general-information-exposure-in-keycloak-user)
- [Ansible discloses sensitive information in traceback error message](https://junglewise.ai/threats/cve-2021-3620-ansible-discloses-sensitive-information-in-traceback-error-message)