CVE-2026-125063: automation controller · ReDoS
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 9 Nov 2026, 19:21 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 4.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9 | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2ansible-automation-platform-27/controller-rhel9 | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2automation-controller | Affected– | Fixed in– |
AI-suggested
The schedule preview endpoint is accessible to any authenticated user and cannot be restricted by RBAC, so exposure can only be reduced by limiting API access to trusted users. Red Hat recommends applying the fix that replaces the inefficient regex validation with anchored patterns or explicit token searches, parses the submitted value once, and caps the accepted rrule length before validation. Until patched, controlling authenticated user access to the API is the primary mitigation.
Description
A vulnerability in the rrule validation logic of the automation controller component in Red Hat Ansible Automation Platform allows an authenticated user to cause a denial of service. The issue arises from inefficient regular expressions that cause validation time to grow quadratically when expected tokens are missing. This can exhaust API web workers, denying access to the API and web UI. The impact is limited to availability with no confidentiality or integrity effects.