{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-123036", "assignerOrgId": "53f830b8-0a3f-465b-8143-3b8a9948e749", "state": "PUBLISHED", "assignerShortName": "redhat", "dateReserved": "2026-11-05T07:01:00.146Z", "datePublished": "2026-11-05T09:38:31.304Z", "dateUpdated": "2026-11-05T19:04:44.264Z"}, "containers": {"cna": {"descriptions": [{"lang": "en", "value": "A flaw was found in ansible-core. When a task marked `no_log: true` fails, the task result is censored before being emitted, but the `exception` field is retained because it is present in the PRESERVE allow-list in lib/ansible/_internal/_task.py, and the default stdout callback prints it through CallbackBase._handle_exception. As a result, sensitive values the operator explicitly asked to hide can be disclosed: module argument-validation errors echo the argument value, templating errors print an Origin source snippet (the failing line plus the two preceding lines of the variables file, exposing neighbouring secrets from an -e @secrets.yml file), and fail/assert messages are printed in full. Secret material supplied as extra variables or variables files can therefore leak to terminal output, CI logs, and the stdout logs of any automation wrapping ansible-playbook, even though every task touching the secrets is marked no_log: true. This is a regression introduced with the ansible-core 2.19 data-tagging/templating rework; the behaviour does not occur on 2.16, where the error text is correctly censored."}], "affected": [{"vendor": "Red Hat", "product": "ansible-core", "packageName": "ansible-core", "collectionURL": "https://pypi.org/project/ansible-core/", "defaultStatus": "unaffected", "versions": [{"version": "2.19.0", "status": "affected", "lessThan": "2.23.0", "versionType": "semver"}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-209", "description": "CWE-209 Generation of Error Message Containing Sensitive Information"}]}], "references": [{"url": "https://access.redhat.com/security/cve/CVE-2026-123036"}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "baseScore": 5.5, "baseSeverity": "MEDIUM"}}], "providerMetadata": {"orgId": "53f830b8-0a3f-465b-8143-3b8a9948e749", "shortName": "redhat", "dateUpdated": "2026-11-05T09:38:31.304Z"}, "x_generator": {"engine": "cvelib 1.8.0"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-11-05T16:41:30.073071Z", "id": "CVE-2026-123036", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-11-05T19:04:44.264Z"}}]}}

{}

{"affected": [{"affectedData": [{"collectionURL": "https://pypi.org/project/ansible-core/", "defaultStatus": "unaffected", "packageName": "ansible-core", "product": "ansible-core", "vendor": "Red Hat", "versions": [{"lessThan": "2.23.0", "status": "affected", "version": "2.19.0", "versionType": "semver"}]}], "source": "secalert@redhat.com"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "A flaw was found in ansible-core. When a task marked `no_log: true` fails, the task result is censored before being emitted, but the `exception` field is retained because it is present in the PRESERVE allow-list in lib/ansible/_internal/_task.py, and the default stdout callback prints it through CallbackBase._handle_exception. As a result, sensitive values the operator explicitly asked to hide can be disclosed: module argument-validation errors echo the argument value, templating errors print an Origin source snippet (the failing line plus the two preceding lines of the variables file, exposing neighbouring secrets from an -e @secrets.yml file), and fail/assert messages are printed in full. Secret material supplied as extra variables or variables files can therefore leak to terminal output, CI logs, and the stdout logs of any automation wrapping ansible-playbook, even though every task touching the secrets is marked no_log: true. This is a regression introduced with the ansible-core 2.19 data-tagging/templating rework; the behaviour does not occur on 2.16, where the error text is correctly censored."}], "id": "CVE-2026-123036", "lastModified": "2026-11-05T19:17:17.220", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "NONE", "baseScore": 5.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 3.6, "source": "secalert@redhat.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-123036", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-11-05T16:41:30.073071Z", "version": "2.0.3"}}]}, "published": "2026-11-05T10:16:38.220", "references": [{"source": "secalert@redhat.com", "url": "https://access.redhat.com/security/cve/CVE-2026-123036"}], "sourceIdentifier": "secalert@redhat.com", "vulnStatus": "Awaiting Analysis", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-209"}], "source": "secalert@redhat.com", "type": "Secondary"}]}

{"acknowledgement": "Red Hat would like to thank Maksym Mazura (JSC GTRPC Zorya-Mashproekt) for reporting this issue.", "bugzilla": {"description": "ansible-core: no_log does not censor the task exception field, leaking secret values via the default stdout callback", "id": "2567188", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2567188"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "status": "draft"}, "cwe": "CWE-209", "details": ["A flaw was found in ansible-core. When a task marked `no_log: true` fails, the task result is censored before being emitted, but the `exception` field is retained because it is present in the PRESERVE allow-list in lib/ansible/_internal/_task.py, and the default stdout callback prints it through CallbackBase._handle_exception. As a result, sensitive values the operator explicitly asked to hide can be disclosed: module argument-validation errors echo the argument value, templating errors print an Origin source snippet (the failing line plus the two preceding lines of the variables file, exposing neighbouring secrets from an -e @secrets.yml file), and fail/assert messages are printed in full. Secret material supplied as extra variables or variables files can therefore leak to terminal output, CI logs, and the stdout logs of any automation wrapping ansible-playbook, even though every task touching the secrets is marked no_log: true. This is a regression introduced with the ansible-core 2.19 data-tagging/templating rework; the behaviour does not occur on 2.16, where the error text is correctly censored."], "mitigation": {"lang": "en:us", "value": "Until a fixed ansible-core is installed, do not rely solely on `no_log: true` to protect secrets in tasks that may fail; restrict read access to playbook output, CI job logs, and any stdout captured by wrapper automation. As provided by the reporter, deploy a custom stdout callback derived from `default` that overrides _handle_exception to suppress or replace the exception text for results containing the `censored` marker."}, "name": "CVE-2026-123036", "public_date": "2026-11-05T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-123036\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-123036"], "statement": "This flaw affects ansible-core 2.19 and later (the data-tagging/templating rework). Ansible Automation Platform 2.6 and 2.7 ship an affected ansible-core and are affected; AAP 2.4 and 2.5 ship ansible-core 2.18 or earlier, which does not contain the vulnerable code path, and are not affected. The fix will be delivered through ansible-core; products that bundle ansible-core receive it via rebuild.", "threat_severity": "Moderate"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[2.19.0,2.23.0)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "ansible-core", "source": "cna", "vendor": "Red Hat"}, "product": "ansible_core", "vendor": "redhat"}], "created": "2026-11-05T10:30:15.724643+00:00", "title": "Sensitive Data Leakage Exploited by Exception Handling in ansible-core", "updated": "2026-11-05T10:45:14.658110+00:00", "vendors": ["redhat", "redhat$PRODUCT$ansible_core"]}