Red HatCVE-2026-84716

A flaw was found in the automation-controller instance install-bundle endpoint

Red Hat

CVE-2026-84716 · Published Sep 23, 2026 · updated Nov 6, 2026

Medium6.6

No fix yet

Red Hat advisory

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

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...

Affected versions

The source does not list versions here. See the source advisory for affected products and fixes.

Details and references

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.

CVSS 3.1: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N
Severity from: the vendor (its own CVE record or advisory)
Weakness: CWE-266

More Red Hat advisories

All Red Hat

High 7.5Sep 23

Red Hat OpenShift console: path traversalCVE-2026-75887no fix yet High 7.2Sep 23

Red Hat OpenShift Container Platform 4: attacker could send requestsCVE-2026-75886no fix yet High 7.8Sep 23

Red Hat librsvg.: use after freeCVE-2026-96889no fix yet Medium 6.6Sep 23

Red Hat: argument injectionCVE-2026-84724no fix yet High 7.2Sep 23

A flaw was found in the Ansible Automation Platform automation controllerCVE-2026-85475no fix yet High 7.1Sep 23

Red Hat: incomplete denylistCVE-2026-84714no fix yet