CVE-2026-71299 json
Maestro: maestro: rest api write endpoints registered without authentication middleware
published 2026-10-05 34 d ago modified 2026-10-07 32 d ago also EUVD-2026-92758
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
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).
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-71299 updated cvss 6.5
maestro: maestro: REST API write endpoints registered without authentication middleware
-
Red Hat Multicluster Engine for Kubernetes multicluster-engine/maestro-rhel9, multicluster-engine/cloudevents-conductor-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 32 d ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Red Hat Multicluster Engine for Kubernetes
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
access.redhat.com
/security/cve/CVE-2026-71299
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2511520
issue-tracking
Sources
- CVE List CVE-2026-71299
- NVD CVE-2026-71299
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.