CVE-2026-84716

Automation-controller: automation-controller: instance install_bundle issues 10-year, non-revocable receptor mesh-ca certificates for caller-chosen (and case-variant impersonating) hostnames

  • Medium 6.6

Description

A flaw was found in the automation-controller instance install-bundle endpoint. When a System Administrator downloads an execution/hop node's install bundle, the controller signs an X.509 certificate with the receptor mesh certificate authority in which the Common Name, DNS subject-alternative-name, and receptor node-id are taken verbatim from the caller-chosen instance hostname, with a hard-coded ten-year validity, a random serial, and no issuance log or revocation list. Because the hostname charset validator is case-insensitive while the uniqueness validator is case-sensitive, an administrator can register a case variant of an existing control node's hostname and obtain a mesh-CA-signed certificate that TLS peers, which match hostnames case-insensitively, accept as that control node. In managed/hosted deployments — where the customer holds controller superuser but the platform operator runs the mesh — this yields a long-lived, non-revocable mesh peer credential and, with an on-path position, TLS impersonation or interception of control/hybrid mesh nodes. It does not grant direct remote code execution, because receptor work submission is gated by a separate signing key not included in the bundle.

Key facts

Published
23 Sep 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.178% likely to be exploited in the next 30 days, higher than 7.463% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.6CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 8
  • Default status: affected
  • 0:4.6.33-1.el8ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 8
  • Default status: affected
  • 0:4.6.33-1.el8ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 9
  • Default status: affected
  • 0:4.6.33-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 9
  • Default status: affected
  • 0:4.6.33-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6 for RHEL 9
  • Default status: affected
  • 0:4.7.17-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6 for RHEL 9
  • Default status: affected
  • 0:4.7.17-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6
  • Default status: affected
  • 1789673739 up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.7
  • Default status: affected
  • 1789580684 up to but excluding * (unaffected)

Timeline

  1. 2 Sep 2026 Reported to Red Hat.
  2. 23 Sep 2026 Made public.
  3. 23 Sep 2026 Published

Weakness

References