GHSA-3m93-m4q6-mc6v is a medium-severity (CVSS 6.5) CWE-117 vulnerability in ansible. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-3m93-m4q6-mc6v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible
Real-World Exposure
ansible🐍ansible🐍ansibleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ansible | ≥ 2.7.0a1&&< 2.7.15 | 2.7.15 |
| 🐍PyPI | ansible | ≥ 2.8.0a1&&< 2.8.7 | 2.8.7 |
| 🐍PyPI | ansible | ≥ 2.9.0a1&&< 2.9.1 | 2.9.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ansible to 2.7.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3m93-m4q6-mc6v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3m93-m4q6-mc6v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-3m93-m4q6-mc6v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
* The exploitation of this flaw depends on the use of either Sumo Logic or Splunk callback plugins. However, because Red Hat OpenStack Platform (RHOSP) does not use Sumo Logic or Splunk, Red Hat will not be providing a fix for RHOSP Ansible at this time. * Red Hat Gluster Storage no more maintains its own version of…
Frequently Asked Questions
Is GHSA-3m93-m4q6-mc6v in your dependencies?
O3 detects GHSA-3m93-m4q6-mc6v across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.