Medium · CVSS 6.5CVE-2026-71299

Maestro: maestro: rest api write endpoints registered without authentication middlewareCVE-2026-71299

Answer in brief

CVE-2026-71299 records a Medium severity (CVSS 6.5) vulnerability in Maestro: maestro: rest api write endpoints registered without authentication middleware. The current sources do not mark it as known exploited. The current feed maps Red Hat/multicluster-engine/cloudevents-conductor-rhel9 (generic), Red Hat/multicluster-engine/maestro-rhel9 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 5, 2026Updated Oct 5, 2026Source checked Oct 5, 2026First seen by HOL Oct 5, 2026Material review Oct 5, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/multicluster-engine/cloudevents-conductor-rhel9 (generic), Red Hat/multicluster-engine/maestro-rhel9 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Red Hat/multicluster-engine/cloudevents-conductor-rhel9generic	*	Not reported
Red Hat/multicluster-engine/maestro-rhel9generic	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Red Hat/multicluster-engine/cloudevents-conductor-rhel9, Red Hat/multicluster-engine/maestro-rhel9.
Review the reported fix. Source-reported 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.

Evidence timeline and material changes

Published upstream
Oct 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 5, 2026

Sources and claim methodology

Upstream source 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).

Quoted source text, attributed separately from HOL analysis.