# CVE-2026-92750: Harness through 3.3.0 Missing Access Control via infraproviders endpoint

> Authenticated users can access infrastructure provider configurations from unauthorized spaces, exposing sensitive metadata like Docker endpoints and cloud identifiers.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-38q4-gjc8-cq8c

## What is CVE-2026-92750?

CVE-2026-92750 is a high-severity missing authorization vulnerability in harness, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Harness through 3.3.0 omits access control validation in the infrastructure provider read endpoint, allowing authenticated users to retrieve provider configurations from spaces they do not belong to. Attackers can query the GET /api/v1/infraproviders endpoint with arbitrary space identifiers to expose sensitive provider metadata including Docker endpoints, TLS certificate paths, and cloud project identifiers.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92750 is a high-severity missing authorization vulnerability in harness, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92750 in the wild and no public exploit code.

Affected product: harness. 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-92750/ (Markdown: https://insights.sbomify.com/CVE-2026-92750/index.md)
```

## Sources

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

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