UBUNTU-CVE-2026-126642 (CVE-2026-126642)
Vulnerability from osv_ubuntu – Published: 2026-11-12 00:00 – Updated: 2026-11-13 18:04 – Source websiteAn incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller's Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related('webhook_credential', Credential, ..., role_field='use_role') call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential's type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template's webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim's token to a destination the attacker can influence. This may disclose another user's personal access token and allow whatever actions that token permits.
{
"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": "An incorrect authorization flaw was found in AWX, the automation controller component of Red Hat Ansible Automation Platform. The API access classes for JobTemplate and WorkflowJobTemplate do not check the caller\u0027s Credential use_role when assigning the single-valued webhook_credential foreign key: JobTemplateAccess.can_add/can_change and WorkflowJobTemplateAccess.can_change in awx/main/access.py omit the check_related(\u0027webhook_credential\u0027, Credential, ..., role_field=\u0027use_role\u0027) call that UnifiedCredentialsMixin.can_attach performs for the normal many-to-many credentials relationship, and the serializer validates only the credential\u0027s type and namespace. A user who may administer their own job template (or workflow job template) and use its project and inventory can therefore attach a webhook token credential (for example a GitLab token) that they do not have use permission on. The template administrator can retrieve the template\u0027s webhook key; a subsequent webhook event causes AWX to decrypt the attached token and send it in the request header (for GitLab, PRIVATE-TOKEN) to a status URL derived from the event payload, disclosing the victim\u0027s token to a destination the attacker can influence. This may disclose another user\u0027s personal access token and allow whatever actions that token permits.",
"id": "UBUNTU-CVE-2026-126642",
"modified": "2026-11-13T18:04:42Z",
"published": "2026-11-12T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-126642"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-126642"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-126642"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2571729"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-126642"
]
}
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.
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.
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.