Description
A flaw was found in Red Hat Ansible Automation Platform's automation-controller. When a
custom credential type is created or updated, the injector configuration is validated by
rendering each attacker-supplied Jinja2 template synchronously inside the web request
worker, with no limit on iteration count, output size, or execution time. An
authenticated superuser can submit a credential type whose injector contains deeply
nested loops or large string operations, consuming CPU and wall-clock time in the web
worker until it is killed by the request timeout; issuing enough concurrent requests
places all web workers into a kill-and-respawn loop, making the Controller API and UI
unavailable for the duration of the attack. Additionally, certain template constructs
raise exception types that the validator does not handle, resulting in an unhandled
server error (HTTP 500) instead of a clean validation error. The rendering sandbox
prevents code execution, so there is no confidentiality or integrity impact.
Published: n/a
Score: 4.9 Medium
EPSS: n/a
KEV: No
Impact: Denial of Service through uncontrolled resource consumption
Action: Patch
AI Analysis

Impact

The vulnerability exists in the credential type injector validation in Red Hat Ansible Automation Platform. Attacker‑supplied Jinja2 templates are rendered synchronously inside the web worker during credential type creation or update, with no limits on loop depth, output size or execution time. An authenticated superuser can submit a template that consumes excessive CPU and wall‑clock time, causing the worker to hang until the request times out. If enough concurrent requests are issued, all web workers are killed and respawned, making the Controller API and UI unavailable. In some cases, ill‑formed templates produce unhandled exceptions, leading to HTTP 500 responses instead of clean validation errors. The sandboxed rendering environment prevents code execution, so there is no confidentiality or integrity impact – only availability is compromised.

Affected Systems

This issue affects Red Hat Ansible Automation Platform version 2.6 running on Enterprise Linux 9, as identified by the CPE cpe:/a:redhat:ansible_automation_platform:2.6::el9. No patch version ranges were specified, so any release built from this code base is potentially vulnerable.

Risk and Exploitability

The CVSS score of 4.9 denotes a moderate severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, exploitation requires authenticated superuser privileges and the use of the /api/controller/v2/credential_types/ endpoint; the likely attack vector therefore appears to be remote via an authorized API call. The impact is limited to service availability, and the attack requires privileged access, so the overall risk is moderate but can be significant in production deployments where the API is heavily used.

Generated by OpenCVE AI on September 24, 2026 at 03:05 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Red Hat Ansible Automation Platform to the latest release that contains this fix.
  • If a patch is not immediately available, temporarily deny superusers the ability to create or modify custom credential types until remediation is applied.
  • Configure or enforce server‑side limits on Jinja2 rendering time, iteration count, or output size, and consider increasing request timeouts or disabling the credential type endpoint during periods of high load to mitigate potential service disruption.

Generated by OpenCVE AI on September 24, 2026 at 03:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 24 Sep 2026 00:15:00 +0000

Type Values Removed Values Added
Description A flaw was found in Red Hat Ansible Automation Platform's automation-controller. When a custom credential type is created or updated, the injector configuration is validated by rendering each attacker-supplied Jinja2 template synchronously inside the web request worker, with no limit on iteration count, output size, or execution time. An authenticated superuser can submit a credential type whose injector contains deeply nested loops or large string operations, consuming CPU and wall-clock time in the web worker until it is killed by the request timeout; issuing enough concurrent requests places all web workers into a kill-and-respawn loop, making the Controller API and UI unavailable for the duration of the attack. Additionally, certain template constructs raise exception types that the validator does not handle, resulting in an unhandled server error (HTTP 500) instead of a clean validation error. The rendering sandbox prevents code execution, so there is no confidentiality or integrity impact.
Title automation-controller: automation-controller: CredentialType injector validation renders attacker-supplied Jinja2 templates synchronously in the web worker, allowing uncontrolled resource consumption (denial of service) and an unhandled-exception (500) via /api/controller/v2/credential_types/
First Time appeared Redhat
Redhat ansible Automation Platform
Weaknesses CWE-1050
CPEs cpe:/a:redhat:ansible_automation_platform:2.6::el9
Vendors & Products Redhat
Redhat ansible Automation Platform
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Subscriptions

Redhat Ansible Automation Platform
cve-icon MITRE

No data.

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-23T00:00:00Z

Links: CVE-2026-84709 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-24T18:00:19Z

Weaknesses
  • CWE-1050

    Excessive Platform Resource Consumption within a Loop