High [CVE-2026-66804] Authenticated SSRF via user-controlled towerHost in /ansibletower handler
This high-severity Red Hat Linux advisory covers CVE-2026-66804 affecting multicluster engine for Kubernetes 2.11, multicluster engine for Kubernetes 2.17, multicluster engine for Kubernetes 2.6.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
Improper access control in Windows Cross Device Service allows an authorized attacker to elevate privileges locally. A flaw was found in the console component.
An authenticated user can exploit a Server-Side Request Forgery (SSRF) vulnerability by manipulating the `towerHost` parameter when accessing the `/ansibletower` handler. This allows the user to bypass pathname validation and access arbitrary internal or external hosts.
The primary consequence is the exfiltration of full HTTP responses, leading to information disclosure from the affected system. Red Hat severity: Important — CVSS 7.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Weakness: CWE-918.
Affected Red Hat products: multicluster engine for Kubernetes 2.1; multicluster engine for Kubernetes 2.11; multicluster engine for Kubernetes 2.17; multicluster engine for Kubernetes 2.6; multicluster engine for Kubernetes 2.8; multicluster engine for Kubernetes 2.9; Red Hat Advanced Cluster Management for Kubernetes 2.11; Red Hat Advanced Cluster Management for Kubernetes 2.13; Red Hat Advanced Cluster Management for Kubernetes 2.14; Red Hat Advanced Cluster Management for Kubernetes 2.15; Red Hat Advanced Cluster Management for Kubernetes 2.16; Red Hat Advanced Cluster Management for Kubernetes 2.17.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 28 days ago·verify at source
- multicluster-engine/console-mce-rhel9:1787079364
- multicluster-engine/console-mce-rhel9:1786911977
- multicluster-engine/console-mce-rhel9:1786668856
- multicluster-engine/console-mce-rhel9:1787264250
- multicluster-engine/console-mce-rhel9:1787259048
- multicluster-engine/console-mce-rhel9:1787079359
- rhacm2/console-rhel9:1787687062
- rhacm2/console-rhel9:1787339249
- rhacm2/console-rhel9:1787339248
- rhacm2/console-rhel9:1787341780
- rhacm2/console-rhel9:1786908361
- rhacm2/console-rhel9:1787335105
- RHSA-2026:59557
- RHSA-2026:57194
- RHSA-2026:59593
- RHSA-2026:59579
- RHSA-2026:59558
- RHSA-2026:59559
- RHSA-2026:60387
- RHSA-2026:60390
- RHSA-2026:60388
- RHSA-2026:60389
- RHSA-2026:57191
- RHSA-2026:60386
Official advisory · high-confidence parse· fetched 28 days ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 28 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.