CVE-2026-71299

Maestro: maestro: rest api write endpoints registered without authentication middleware

Published Oct 5, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
A flaw was found in Maestro. Its REST API write endpoints were registered without proper authentication middleware. This allows a remote attacker to perform unauthorized write operations, such as creating, modifying, or deleting consumers and resource bundles. This could lead to data integrity issues or a denial of service (DoS).

Analysis

AI-generated

Technical impact

Maestro’s REST API write endpoints were registered without authentication middleware, allowing a remote attacker to perform unauthorized write operations such as creating, modifying, or deleting consumers and resource bundles. This vulnerability can compromise data integrity and may lead to service disruption. The weakness corresponds to CWE‑306, improper restriction of undue privileges.

Affected Systems

The affected product is Red Hat Multicluster Engine for Kubernetes. No specific version information is provided in the CNA data, indicating that all versions of this product are potentially impacted unless mitigated at the deployment level.

Risk and Exploitability

The CVSS score of 6.5 indicates medium severity, and the EPSS score is not available, suggesting no current data on exploit probability. The vulnerability is not listed in the CISA KEV catalog. The lack of authentication middleware allows unauthenticated remote attackers to exploit the exposed API endpoints, posing a moderate risk to the integrity and availability of the Multicluster Engine environment.

Remediation

Vendor Workaround

To mitigate this issue, disable the OpenShift Route for the Maestro component if external authentication is not configured. This can be achieved by setting `route.enabled=false` in the Maestro Helm chart configuration. Alternatively, implement an external authentication layer, such as an Istio AuthorizationPolicy, NetworkPolicy, or oauth-proxy, to secure the exposed REST API endpoints. Disabling the route may impact functionality that relies on external access to Maestro's REST API.


OpenCVE Recommended Actions

  • Disable the OpenShift Route for Maestro by setting "route.enabled=false" in the Helm chart configuration to block external access to the REST API.
  • Implement an external authentication layer such as an Istio AuthorizationPolicy, NetworkPolicy, or oauth‑proxy to secure the exposed REST API endpoints.
  • Apply the latest Red Hat update or patch for Multicluster Engine when it becomes available to resolve the authentication deficiency.

Generated by OpenCVE AI on October 5, 2026 at 21:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Maestro
Maestro maestro
Redhat multicluster Engine For Kubernetes
Vendors & Products Maestro
Maestro maestro
Redhat multicluster Engine For Kubernetes
Type Values Removed Values Added
Description A flaw was found in Maestro. Its REST API write endpoints were registered without proper authentication middleware. This allows a remote attacker to perform unauthorized write operations, such as creating, modifying, or deleting consumers and resource bundles. This could lead to data integrity issues or a denial of service (DoS).
Title Maestro: maestro: rest api write endpoints registered without authentication middleware
First Time appeared Redhat
Redhat multicluster Engine
Weaknesses CWE-306
CPEs cpe:/a:redhat:multicluster_engine
Vendors & Products Redhat
Redhat multicluster Engine
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Oct 7, 2026, 8:13 PM
Reserved
Aug 5, 2026, 2:50 PM
Status
Awaiting Analysis
Published
Oct 5, 2026, 8:17 PM
Modified
Oct 7, 2026, 9:17 PM
Severity
Moderate
Public date
Oct 5, 2026, 5:38 PM