CVE-2026-71298: Red Hat Multicluster Engine for Kubernetes · SQL Injection
Affects Red Hat Multicluster Engine for KubernetesSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 18 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 6.4 |
|---|
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Multicluster Engine for Kubernetesmulticluster-engine/cloudevents-conductor-rhel9 | Affected– | Fixed in– |
| Multicluster Engine for Kubernetesmulticluster-engine/maestro-rhel9 | Affected– | Fixed in– |
AI-suggested
Red Hat advises restricting network access to the Maestro REST API list endpoints to trusted clients only by implementing firewall rules or network segmentation. If the Maestro service is not essential, consider disabling it.
Description
CVE-2026-71298 is a SQL injection vulnerability in the orderBy query parameter of the REST API list endpoints in Red Hat Multicluster Engine for Kubernetes's Maestro component. This flaw allows unauthenticated remote attackers to perform read-only blind extraction of data from the database. The vulnerability is rated as moderate severity because it only permits data disclosure without modification or command execution. Maestro endpoints are typically deployed within internal cluster networks, limiting exposure to untrusted external parties. Mitigation involves restricting network access to trusted clients or disabling the Maestro service if not needed.