{"id":"CVE-2026-84716","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-84716","generatedAt":"2026-10-28T05:26:45.206Z","title":"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…","description":"A flaw was found in the automation-controller instance\n                  install-bundle endpoint. When a System Administrator downloads\n                  an execution/hop node's install bundle, the controller signs an\n                  X.509 certificate with the receptor mesh certificate authority\n                  in which the Common Name, DNS subject-alternative-name, and\n                  receptor node-id are taken verbatim from the caller-chosen\n                  instance hostname, with a hard-coded ten-year validity, a random\n                  serial, and no issuance log or revocation list. Because the\n                  hostname charset validator is case-insensitive while the\n                  uniqueness validator is case-sensitive, an administrator can\n                  register a case variant of an existing control node's hostname\n                  and obtain a mesh-CA-signed certificate that TLS peers, which\n                  match hostnames case-insensitively, accept as that control node.\n                  In managed/hosted deployments — where the customer holds\n                  controller superuser but the platform operator runs the mesh —\n                  this yields a long-lived, non-revocable mesh peer credential and,\n                  with an on-path position, TLS impersonation or interception of\n                  control/hybrid mesh nodes. It does not grant direct remote code\n                  execution, because receptor work submission is gated by a\n                  separate signing key not included in the bundle.","published":"2026-09-23T20:17:18.000Z","lastModified":"2026-09-24T16:17:13.000Z","status":"Awaiting Analysis","sourceIdentifier":"secalert@redhat.com","cvss":{"version":"3.1","score":6.6,"severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N"},"cwe":["CWE-266"],"affected":[],"epss":{"score":0.00178,"percentile":0.07333,"date":"2026-10-27","history":[{"date":"2026-09-24","score":0.00178,"percentile":0.06517}]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.18%). Track it; it rarely justifies an emergency change on its own."},"changes":[{"kind":"new","label":"New CVE","at":"2026-09-23T20:17:18.000Z","detail":{"score":"6.6","severity":"MEDIUM","publishedAt":"2026-09-23T20:17:18.210Z"},"summary":"New CVE, medium severity (CVSS 6.6)."}],"references":[{"url":"https://access.redhat.com/errata/RHSA-2026:71113","source":"secalert@redhat.com"},{"url":"https://access.redhat.com/errata/RHSA-2026:71114","source":"secalert@redhat.com"},{"url":"https://access.redhat.com/errata/RHSA-2026:71177","source":"secalert@redhat.com"},{"url":"https://access.redhat.com/errata/RHSA-2026:71179","source":"secalert@redhat.com"},{"url":"https://access.redhat.com/security/cve/CVE-2026-84716","source":"secalert@redhat.com"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2527199","source":"secalert@redhat.com"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-84716","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}