Information Disclosure in ansible (CVE-2025-14010)
Summary
Vulnerability in ansible (CVE-2025-14010). Confidential information can be exposed externally. Mitigation: upgrade to 12.2.0 or later.
Original description
The description as published by the source.
A flaw was found in ansible-collection-community-general. This vulnerability allows for information exposure (IE) of sensitive credentials, specifically plaintext passwords, via verbose output when running Ansible with debug modes. Attackers with access to logs could retrieve these secrets and potentially compromise Keycloak accounts or administrative access.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-14010 has been found in ansible.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade ansible to 12.2.0 or later.
If unsure, ask your IT team or search "ansible CVE-2025-14010" on the vendor's site.
CVE-2025-14010 (ansible) — CWE-200 / CVSS v3 5.5
Attack vector: local / no user interaction
Patched: 12.2.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in ansible.
Check the vendor advisory for the affected versions of ansible.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 12.2.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ansible' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ansible' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ansibleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ansible to 12.2.0ステージング環境で 12.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-14010 ansible Fixed in: 12.0.0+dfsg-0+deb13u1
- Ubuntu UBUNTU-CVE-2025-14010 ansible
References
- advisory access.redhat.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- report bugzilla.redhat.com
- report github.com
- web github.com
- web github.com
- web github.com
- web access.redhat.com