CVE-2026-71475

What it is

A flaw was found in insights-client. A compromised managed cluster, referred to as a 'spoke', can inject unencoded data into the Insights API URL path. This occurs because the ClusterID, which is controlled by the spoke, is used directly in the request path without proper validation or URL encoding. This vulnerability allows a malicious spoke to redirect authenticated requests to unintended API endpoints, potentially leading to information disclosure or unauthorized access.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data exposure.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-11 20:18 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-24 15:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 6.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-08-11 20:18 UTC

Last modified

2026-10-24 15:10 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-22 · Path traversal

Record status

Modified

Affected

• Redhat Advanced Cluster Management For Kubernetes 2.0
• Redhat insights-client

Attack profile CVSS 3.1 · 6.8

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-71475.md and follow it. Check whether this project is affected by CVE-2026-71475. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge