CVE-2026-92750
Harness through 3.3.0 omits access control validation in the …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/harness/harness
- github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider/find.go#L25-L41
- github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider/list.go#L37
- github.com/harness/harness/issues/3697
- www.vulncheck.com/advisories/harness-through-3.3.0-missing-access-control-via-infraprovide
- nvd.nist.gov/vuln/detail/CVE-2026-92750
- cve.org/CVERecord?id=CVE-2026-92750
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.