CVE-2026-115622
Awaiting Analysis Awaiting Analysis - Queue

Information Disclosure in Ansible-Core via Warning Messages

Vulnerability report for CVE-2026-115622, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: redhat-SADP

Description

A flaw was found in ansible-core. When a task or its parameters are marked no_log: true, sensitive values passed to a module's warn() or deprecate() calls are not redacted and are printed in cleartext to stdout/stderr in warning and deprecation messages. The 'warnings' and 'deprecations' keys are retained in the PRESERVE allow-list in lib/ansible/_internal/_task.py when the task result is censored, so sensitive parameters bypass masking and can be disclosed in output captured in terminal sessions, CI logs, and any automation wrapping ansible-playbook, even though every task touching the secrets is marked no_log: true.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Red Hat ansible-core From 2.19.0 (inc) to 2.22.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-532 The product writes sensitive information to a log file.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in ansible-core allows sensitive values to be exposed in warning or deprecation messages even when tasks are marked no_log: true. Normally, no_log should redact sensitive data, but when a module uses warn() or deprecate() with such values, they appear in cleartext in stdout or stderr. This bypasses intended masking and could leak secrets in logs or CI outputs.

Detection Guidance

This vulnerability can be detected by reviewing Ansible playbook outputs for any warning or deprecation messages that expose sensitive data despite no_log: true settings. Check CI logs, terminal sessions, and automation outputs for plaintext secrets in warnings.

Impact Analysis

If exploited, this flaw could expose sensitive data like passwords or API keys in plaintext during playbook execution. Attackers with access to logs or terminal output could capture these secrets, leading to unauthorized access or data breaches. It undermines security controls designed to protect confidential information.

Compliance Impact

This vulnerability could violate compliance requirements like GDPR or HIPAA by exposing personal or health data in logs. Regulations mandate strict protection of sensitive data, and accidental disclosure due to this flaw may result in legal penalties or loss of certification.

Mitigation Strategies

Review all playbooks to ensure no_log: true is properly applied to tasks handling sensitive data. Avoid using warn() or deprecate() with sensitive parameters. Update ansible-core to the latest patched version if available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-115622. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...