UBUNTU-CVE-2026-123036 (CVE-2026-123036)
Vulnerability from osv_ubuntu – Published: 2026-11-05 00:00 – Updated: 2026-11-05 00:00 – Source website
VLAI
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.
Severity
5.5 (Medium)
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "1.5.4+dfsg-1ubuntu0.1~esm3"
},
{
"binary_name": "ansible-fireball",
"binary_version": "1.5.4+dfsg-1ubuntu0.1~esm3"
},
{
"binary_name": "ansible-node-fireball",
"binary_version": "1.5.4+dfsg-1ubuntu0.1~esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@1.5.4+dfsg-1ubuntu0.1~esm3?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1+dfsg-1",
"1.3.4+dfsg-1",
"1.4.0+dfsg-1",
"1.4.1+dfsg-1",
"1.4.3+dfsg-1",
"1.4.4+dfsg-1",
"1.5.4+dfsg-1",
"1.5.4+dfsg-1ubuntu0.1~esm1",
"1.5.4+dfsg-1ubuntu0.1~esm2",
"1.5.4+dfsg-1ubuntu0.1~esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "2.0.0.2-2ubuntu1.3+esm6"
},
{
"binary_name": "ansible-fireball",
"binary_version": "2.0.0.2-2ubuntu1.3+esm6"
},
{
"binary_name": "ansible-node-fireball",
"binary_version": "2.0.0.2-2ubuntu1.3+esm6"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@2.0.0.2-2ubuntu1.3+esm6?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.9.2+dfsg-2",
"1.9.4-1",
"2.0.0.2-2",
"2.0.0.2-2ubuntu1",
"2.0.0.2-2ubuntu1.1",
"2.0.0.2-2ubuntu1.2",
"2.0.0.2-2ubuntu1.3",
"2.0.0.2-2ubuntu1.3+esm1",
"2.0.0.2-2ubuntu1.3+esm2",
"2.0.0.2-2ubuntu1.3+esm3",
"2.0.0.2-2ubuntu1.3+esm4",
"2.0.0.2-2ubuntu1.3+esm5",
"2.0.0.2-2ubuntu1.3+esm6"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "2.5.1+dfsg-1ubuntu0.1+esm5"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@2.5.1+dfsg-1ubuntu0.1+esm5?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.3.1.0+dfsg-2",
"2.5.0+dfsg-1",
"2.5.1+dfsg-1",
"2.5.1+dfsg-1ubuntu0.1",
"2.5.1+dfsg-1ubuntu0.1+esm1",
"2.5.1+dfsg-1ubuntu0.1+esm2",
"2.5.1+dfsg-1ubuntu0.1+esm3",
"2.5.1+dfsg-1ubuntu0.1+esm4",
"2.5.1+dfsg-1ubuntu0.1+esm5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "2.9.6+dfsg-1ubuntu0.1~esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@2.9.6+dfsg-1ubuntu0.1~esm3?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.8.3+dfsg-1",
"2.8.6+dfsg-1",
"2.9.2+dfsg-1",
"2.9.4+dfsg-1",
"2.9.6+dfsg-1",
"2.9.6+dfsg-1ubuntu0.1~esm1",
"2.9.6+dfsg-1ubuntu0.1~esm2",
"2.9.6+dfsg-1ubuntu0.1~esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible-core",
"binary_version": "2.12.0-1ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "ansible-core",
"purl": "pkg:deb/ubuntu/ansible-core@2.12.0-1ubuntu0.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.12.0-1",
"2.12.0-1ubuntu0.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm4"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm4?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.10.7+merged+base+2.10.8+dfsg-1",
"2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm1",
"2.10.7+merged+base+2.10.8+dfsg-1ubuntu0.1~esm4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "9.2.0+dfsg-0ubuntu5"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@9.2.0+dfsg-0ubuntu5?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"7.7.0+dfsg-1",
"7.7.0+dfsg-3",
"9.2.0+dfsg-0ubuntu4",
"9.2.0+dfsg-0ubuntu5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible-core",
"binary_version": "2.16.3-0ubuntu2"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "ansible-core",
"purl": "pkg:deb/ubuntu/ansible-core@2.16.3-0ubuntu2?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.14.9-2",
"2.14.11-1",
"2.14.11-2",
"2.14.13-1",
"2.16.3-0ubuntu1",
"2.16.3-0ubuntu2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "13.4.0+dfsg-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@13.4.0+dfsg-1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"13.1.0+dfsg-1ubuntu1",
"13.4.0+dfsg-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible-core",
"binary_version": "2.22.0~beta2-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "ansible-core",
"purl": "pkg:deb/ubuntu/ansible-core@2.22.0~beta2-1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.20.1-1",
"2.21.1~rc1-1",
"2.21.1~rc1-2",
"2.21.1~rc1-2ubuntu1",
"2.22.0~beta2-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible",
"binary_version": "13.1.0+dfsg-1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "ansible",
"purl": "pkg:deb/ubuntu/ansible@13.1.0+dfsg-1ubuntu1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"12.0.0~b1+dfsg-1",
"12.0.0+dfsg-1",
"12.2.0+dfsg-1",
"13.1.0+dfsg-1",
"13.1.0+dfsg-1ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ansible-core",
"binary_version": "2.20.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "ansible-core",
"purl": "pkg:deb/ubuntu/ansible-core@2.20.1-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.19.0-1ubuntu1",
"2.19.4-1",
"2.20.1-1"
]
}
],
"aliases": [],
"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.",
"id": "UBUNTU-CVE-2026-123036",
"modified": "2026-11-05T00:00:00Z",
"published": "2026-11-05T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-123036"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-123036"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-123036"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-123036"
]
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.