Advisory record · GHSA-pm48-cvv2-29q5

In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine 2.6.19, were logging at the DEBUG level which lead to a disclosure of credentials if a plug...

CVSS 7.3 HighEPSS 0.0051 · 44th percentile

Published by the GitHub Advisory Database at 8 Oct 2019, 19:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ansiblePyPI<2.6.20 || >=2.7.0, <2.7.14 || >=2.8.0, <2.8.62.6.20, 2.7.14, 2.8.6
Identifiers
GHSA-pm48-cvv2-29q5 · CVE-2019-14846 · PYSEC-2019-4
Weakness (CWE)
CWE-117 · CWE-532
Published
8 Oct 2019
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Ansible (PyPI package ansible, versions before 2.6.20, 2.7.0 through 2.7.13, and 2.8.0 through 2.8.5) was logging at the DEBUG level, which could expose credentials when a plugin used a library that logged credentials at DEBUG. An attacker would need to be able to read the resulting debug logs; the source does not describe a remote attack path. Upgrade to ansible 2.6.20, 2.7.14, 2.8.6, or later. Modules are not affected because they run in a separate process.

Written 9 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.3 High 3.0 CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0051, the 44th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 8 Oct 2019. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.