# CVE-2026-71475: Insights-client-rhel9: insights-client: spoke-controlled clusterid injected unencoded into insights api url path

> A compromised managed cluster can inject unencoded data into the Insights API URL path, potentially redirecting requests to unintended endpoints for information disclosure.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 5 Sep 2026
- **Also known as:** GHSA-gqvx-3g3q-49g9

## What is CVE-2026-71475?

CVE-2026-71475 is a medium-severity path traversal vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.13, published on 11 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-71475?

It affects 2 products.


Products: Redhat Advanced Cluster Management for Kubernetes, Redhat Insights-Client.

## How do I fix CVE-2026-71475?

No fix has been published for CVE-2026-71475 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71475 being exploited?

There is no known exploitation of CVE-2026-71475 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat Advanced Cluster Management for Kubernetes 2.13

- [CVE-2026-4740](https://insights.sbomify.com/CVE-2026-4740/): Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation (high 8.2)
- [CVE-2023-3027](https://insights.sbomify.com/CVE-2023-3027/): Privilege escalation in RHACM (high 7.8)
- [CVE-2022-3841](https://insights.sbomify.com/CVE-2022-3841/): Server-side request forgery in RHACM (high 7.8)
- [CVE-2026-71474](https://insights.sbomify.com/CVE-2026-71474/): Insights-client-rhel9: insights-client: pull-secret bearer token written to logs on non-200 ccx response (high 7.1)
- [CVE-2026-71846](https://insights.sbomify.com/CVE-2026-71846/): Insights-client: insights-client: clusterrole grants cluster-wide secrets get/list/watch beyond least privilege (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71475 and fix it if it is affected.

What it is: CVE-2026-71475 is a medium-severity path traversal vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.13, published on 11 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71475 in the wild and no public exploit code.

Affected product: Red Hat Advanced Cluster Management for Kubernetes 2.13. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71475/ (Markdown: https://insights.sbomify.com/CVE-2026-71475/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71475
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71475
- OSV: https://osv.dev/vulnerability/CVE-2026-71475

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71475/
Summaries are generated and may contain mistakes; the official description above is the record.