VulnerabilityPublished 26 Sep 2025Updated 7 Nov 2025

CVE-2025-11060: Red Hat OpenShift Service Mesh 3 · Incorrect Authorization

Affects Red Hat OpenShift Service Mesh 3Source CVE Database V5

Not known to be exploited · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat OpenShift Service Mesh 3	Affected =0 =2.2.0 =2.3.0 =3.3.0	Fixed in–

AI-suggested

To mitigate CVE-2025-11060, organizations should prioritize upgrading to patched versions of OpenShift Service Mesh 3 once available from Red Hat. Until patches are released, administrators should restrict access to the live query subscription feature, limiting it to trusted users only. Implement strict network segmentation and access controls to reduce exposure of the affected service to untrusted or low-privilege users. Monitor logs for unusual subscription queries or patterns indicative of crafted LIVE SELECT subscriptions attempting to bypass access controls. Employ role-based access control (RBAC) policies to minimize privileges granted to record or guest users, especially restricting their ability to initiate live queries. Consider disabling live query subscriptions if they are not essential for operational needs. Additionally, conduct regular security audits and penetration testing focused on database access controls and subscription mechanisms. Stay informed on Red Hat advisories for official patches and guidance.

Description

A flaw was found in the live query subscription mechanism of the database engine. This vulnerability allows record or guest users to observe unauthorized records within the same table, bypassing access controls, via crafted LIVE SELECT subscriptions when other users alter or delete records.

Impact

The primary impact of CVE-2025-11060 is unauthorized disclosure of sensitive data due to bypassed access controls in the live query subscription mechanism. Organizations using affected versions of OpenShift Service Mesh 3 may experience confidentiality breaches, potentially exposing sensitive or regulated information to unauthorized users with limited privileges. This can lead to compliance violations, reputational damage, and increased risk of further attacks leveraging leaked data. Since the vulnerability does not affect data integrity or availability, the risk of data manipulation or service disruption is low. However, the ease of exploitation with low privileges and user interaction means attackers inside the network or with limited access could leverage this flaw to escalate data access. Multi-tenant cloud environments, managed service providers, and enterprises with strict data segregation requirements are particularly vulnerable. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as threat actors may develop exploits once the vulnerability details are widely known.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 18:45 UTC

Technical details

References

Community reviews

Related threats