CVE-2026-84717
Automation-controller: automation-controller: unauthenticated 200-vs-403 oracle in bitbucket data center webhook receiver enumerates webhook-enabled job templates
What happened?
A flaw was found in the Ansible Automation Platform automation-controller. The unauthenticated Bitbucket Data Center webhook receiver skips HMAC signature verification for diagnostics:ping events after it has already looked up the target template, causing the endpoint to return HTTP 200 for a template that has a Bitbucket DC webhook configured and HTTP 403 otherwise. An unauthenticated remote attacker can use this response discrepancy as an oracle to enumerate which Job Template and Workflow Job Template IDs have Bitbucket DC webhooks configured, without knowing the secret webhook_key.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el8ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el8ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.7.17-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.7.17-1.el9ap to < * | See vendor advisory |
| ansible-automation-platform-26/controller-rhel9Red Hat | unaffected: 1789673739 to < * | See vendor advisory |
| ansible-automation-platform-27/controller-rhel9Red Hat | unaffected: 1789580684 to < * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-84717
- https://access.redhat.com/errata/RHSA-2026:71113
- https://access.redhat.com/errata/RHSA-2026:71114
- https://access.redhat.com/errata/RHSA-2026:71177
- https://access.redhat.com/errata/RHSA-2026:71179
- https://access.redhat.com/security/cve/CVE-2026-84717
- https://bugzilla.redhat.com/show_bug.cgi?id=2527210