Who is not affected by CVE-2026-125063?

Q: Who is not affected by CVE-2026-125063?

Not affected if: api-not-exposed, no-untrusted-users.

MEDIUM4.3CVSS · secalert@redhat.com

NO KNOWN
EXPLOIT

CVE-2026-125063 · Vendor

Automation controller: crafted schedule rule can stall the web API

NO FIX YET

An authenticated user can submit a very large schedule rule (rrule) with no valid tokens, and the server's validation slows down quadratically. Repeated requests can tie up the web workers and deny access to the API and web UI, with no data exposed.

first public Nov 9, 2026 · 1 source

Could this affect your app?

Free first check from your website. Connect your repo for the full answer.

01 · Who is affected

Teams running Red Hat Ansible Automation Platform automation controller that let users create or preview schedules through the REST API. The flaw needs a logged-in account, but any account that can reach the schedule preview endpoint can trigger it. Installations where only trusted administrators have API access carry less exposure.

Not affected if api-not-exposed, no-untrusted-users

Who cares ansible, automation-controller, self-hosted

02 · How to check

Unknown from the sources.

03 · The fix

No fix yet, per the sources.

Exploited: No reports yet
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 9, 2026

What the sources say, verbatim

757 characters

A flaw was found in the rrule validation of schedules in automation controller. Several non-anchored regular expressions with lazy wildcard prefixes are applied to the user-supplied rrule value; when the expected DTSTART/RRULE tokens are absent, validation time grows quadratically with the length of the value. An authenticated user can submit a large token-free rrule through the REST API, including the schedule preview endpoint, which requires no resource-level permissions; validation runs synchronously in the API web worker, so a single such request occupies a worker for an extended time and repeated requests can exhaust the web worker pool, denying access to the API and web UI while the attack is sustained. The impact is limited to availability.