Skip to main content

Ansible automation-controller CVE-2026-84486

| EUVDEUVD-2026-85548 HIGH
Active Debug Code (CWE-489)
2026-09-23 redhat GHSA-jr99-3x99-6q34
8.2
CVSS 3.1 · Vendor: redhat
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach controller web interface unauthenticated
  2. Delivery
    Query debug root view for endpoint list
  3. Exploit
    Repeatedly invoke debug scheduler endpoints
  4. Execution
    Contend cluster-wide advisory lock
  5. Persist
    Legitimate scheduler runs skipped, workers exhausted
  6. Impact
    Cluster-wide job dispatch stalls for all tenants

Vulnerability Assessment

Weakness
CWE
Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default production builds of Red Hat Ansible Automation Platform automation-controller, because the four debug scheduler endpoints' URL include is not gated on the debug setting and permits any user including unauthenticated clients. The only prerequisite is network reachability to the automation-controller web service. Limiting factors are minimal: exploitation requires no authentication, no user interaction, and no non-default configuration; the main practical limiter is network segmentation restricting who can reach the controller's web tier, plus knowledge of the endpoint paths (which the unauthenticated debug root view itself discloses).

Impact

This is a genuine operational-availability priority, not a high-CVSS-but-low-real-risk paper cut. The CVSS 8.2 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H) is internally consistent with the description: fully remote, low-complexity, no authentication and no user interaction, with high availability impact and low confidentiality impact. The A:H is well-justified because the flaw stalls job dispatch for ALL tenants on a shared automation-controller cluster and exhausts web workers, and C:L reflects the debug-root view leaking the list of debug endpoints. The most dangerous factor is that these debug scheduler endpoints are routed in PRODUCTION builds by default (the URL include is not gated on the debug setting), so no misconfiguration is needed. Signals are limited: no EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so exploitation status is 'no public exploit identified at time of analysis' - but the trivial trigger (repeatedly hitting a URL) means weaponization would be simple if endpoint paths become known. No SSVC decision data was supplied. The only mild conflict is the 'Information Disclosure' tag, which understates the vulnerability since the dominant impact is denial of service (A:H), not confidentiality.

Exploit ScenarioDerived

An unauthenticated attacker who can reach the automation-controller web interface repeatedly requests the four debug scheduler endpoints (discovered via the unauthenticated debug root view that lists them), each request forcing acquisition of the cluster-wide scheduler advisory lock. Because the legitimate scheduler takes the same lock without waiting, real scheduler runs are silently skipped, halting job dispatch for every tenant while controller web workers are tied up. No public POC is identified in the available data, but the attack requires only repeated HTTP requests with no authentication or special tooling.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 23, 2026

Unauthenticated remote attackers can stall job dispatch for every tenant on Red Hat Ansible Automation Platform 2 by repeatedly calling four debug scheduler views that are routed in production builds because their URL include is not gated on the debug setting. Each call lets any network-reachable client acquire the cluster-wide scheduler advisory lock, and since the legitimate scheduler takes that same lock without waiting, genuine scheduler runs are skipped, job dispatch is delayed or halted, and controller web workers are consumed. The debug root view also discloses the list of debug endpoints to unauthenticated callers, and no public exploit code has been identified at time of analysis.

RemediationAI

No vendor-released patch was identified at time of analysis; Red Hat's CVE page (https://access.redhat.com/security/cve/CVE-2026-84486) and Bugzilla 2527085 (https://bugzilla.redhat.com/show_bug.cgi?id=2527085) should be monitored for the fixed automation-controller build and the exact errata version, which should be applied as soon as it is published. Until then, the most effective compensating control is to block the debug scheduler views, and the debug root view that enumerates them, at the ingress layer - a reverse proxy, load balancer, or WAF rule returning 403/404 for those paths - since the routes resolve in production regardless of the debug setting; the trade-off is that operators must maintain the path deny-list and it depends on the proxy being the only path to the controller. Strongly restrict network reachability to the automation-controller web tier with firewall rules or security groups limited to trusted administrative networks, which removes the unauthenticated attack surface but also blocks legitimate user and integration traffic from outside those ranges. Where the deployment is self-managed, consider removing or commenting out the debug URL include and rebuilding, accepting that this is an unsupported local modification that may be reverted by upgrades. Detectively, alert on repeated or abnormal requests to debug-style endpoint paths or on sudden scheduler stalls and web-worker saturation, understanding that this only shortens response time and does not prevent the outage.

Affected VersionsENISA

Red Hat Ansible Automation Platform 2.6 for RHEL 9 patch: 0:4.7.17-1.el9ap

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is classified under CWE-489 (Active Debug Code): development/debug-only views were left reachable in production deployments of the Ansible Automation Platform automation-controller. Four debug views exist that trigger the internal task, dependency, and workflow schedulers; their URL include is not conditioned on the debug setting, so the routes resolve in normal production builds and are configured to accept any user, including unauthenticated clients. The schedulers coordinate across the cluster with a single advisory lock, and the legitimate scheduler path acquires that lock without waiting - so an attacker who holds or repeatedly re-acquires it causes real scheduler runs to be skipped rather than queued. The same requests tie up controller web workers, compounding the availability impact. The debug root view additionally enumerates the debug endpoints for unauthenticated callers, which is the source of the limited confidentiality impact. The CPE records (cpe:2.3:a:red_hat:red_hat_ansible_automation_platform_2:*:*:*:*:*:*:*:*) use wildcard versions, so the supplied data does not constrain the issue to a specific automation-controller release. Under the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H, exploitation requires only network reachability to the automation-controller web tier: no authentication, no user interaction, and no non-default configuration.

Know when Red Hat Ansible Automation Platform 2 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (redhat) PRIMARY 8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
vuln.today AI 8.2 HIGH

Remote, trivial, unauthenticated trigger with no user interaction; cluster-wide job-dispatch denial gives A:H, endpoint-list disclosure gives C:L, no integrity impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
Red Hat 8.2 HIGH

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

DescriptionCVE.org

A flaw was found in Red Hat Ansible Automation Platform's automation- controller. Four debug views that trigger the internal task, dependency, and workflow schedulers are configured to allow any user (including unauthenticated clients) and are routed in production builds because their URL include is not gated on the debug setting. An unauthenticated remote attacker can repeatedly invoke these endpoints to acquire the cluster-wide scheduler advisory lock; because the legitimate scheduler acquires the same lock without waiting, the attacker causes real scheduler runs to be skipped, stalling job dispatch for all tenants, while also consuming controller web workers. The debug root view additionally discloses the list of debug endpoints to unauthenticated callers.

Executive ViewAI

Why It Matters

Red Hat Ansible Automation Platform 2 has a high-severity availability flaw that can delay or halt automated job dispatch for every tenant on an affected controller, disrupting scheduled and on-demand automation across the organization. Repeated requests to four debug scheduler views can consume controller web workers and cause legitimate scheduler runs to be skipped, with no public exploit identified at time of analysis. Because no vendor-released patch has been identified, leadership should prioritize reducing network exposure and monitoring for scheduler and worker degradation.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting network reachability to the controller and the affected debug scheduler endpoints, blocking the four debug view paths at a reverse proxy, load balancer, or WAF, removing or gating the debug URL include in production builds, and monitoring for advisory lock contention, skipped scheduler runs, and worker exhaustion.

Threat Intelligence Overview

EPSS Score
0.5%
Top 58% exploitable
Prevalence
Medium
widely-used enterprise IT automation platform, common but not in every environment
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-84719 CRITICAL
9.9 Sep 23

Missing authorization checks in the Red Hat Ansible Automation Platform 2 automation-controller allow an authenticated o

CVE-2026-84502 CRITICAL
9.9 Sep 23

Authenticated users who hold permission to create or modify a project within a single organization can execute arbitrary

CVE-2026-84474 CRITICAL
9.9 Sep 23

Privilege escalation and remote code execution on managed hosts is possible in Red Hat Ansible Automation Platform 2 bec

CVE-2026-11807 CRITICAL
9.6 Jun 23

Credential disclosure in Red Hat Ansible Automation Platform 2.5 and 2.6 allows any authenticated user to retrieve plain

CVE-2026-12564 CRITICAL
9.6 Aug 18

Server-side request forgery in the Red Hat Ansible Automation Platform 2 Controller's HashiCorp Vault credential plugin

CVE-2026-75884 CRITICAL
9.1 Sep 23

Privilege escalation in Red Hat Ansible Automation Platform 2 (built on the AWX upstream project) lets an authenticated

CVE-2026-12701 CRITICAL
9.0 Jul 20

Arbitrary file write in pulpcore's FilesystemExport feature allows an authenticated administrator to escape the intended

CVE-2026-89091 HIGH
8.8 Oct 08

Symlink-following file overwrite on the Ansible control node is possible in ansible-core when a user runs `ansible-galax

CVE-2026-84683 HIGH
8.7 Sep 23

Stored cross-site scripting in the automation-controller component of Red Hat Ansible Automation Platform 2 lets an auth

CVE-2026-84691 HIGH
8.7 Sep 23

An authenticated automation-controller administrator in Red Hat Ansible Automation Platform 2 can turn the administrator

CVE-2026-92982 HIGH
8.5 Oct 15

Jinja2 template injection in Ansible Operator Plugins (CWE-1336) lets an authenticated Kubernetes user who can create or

CVE-2026-76648 HIGH
8.5 Sep 23

Missing object-level authorization in the JobTemplate copy endpoint (CopyAPIView) of AWX and Red Hat Ansible Automation

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy