# CVE-2026-125063: A flaw was found in the rrule validation of schedules in automation controller.


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-269p-w2wm-cfpf

## What is CVE-2026-125063?

CVE-2026-125063 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 9 Nov 2026. 

### Official description

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.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-125063?


## How do I fix CVE-2026-125063?

No fix has been published for CVE-2026-125063 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125063 being exploited?

There is no known exploitation of CVE-2026-125063 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125063 and fix it if it is affected.

What it is: CVE-2026-125063 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125063 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125063/ (Markdown: https://insights.sbomify.com/CVE-2026-125063/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125063
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125063
- OSV: https://osv.dev/vulnerability/CVE-2026-125063

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125063/
Summaries are generated and may contain mistakes; the official description above is the record.