# CVE-2026-86175: NetBox through 4.7.0 Credential Disclosure via REST and GraphQL APIs

> Authenticated users with view permissions can retrieve plaintext credentials for Git and S3 backends via NetBox APIs, exposing external storage access.

- **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:** 5 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-2fj3-v6qr-qf3j

## What is CVE-2026-86175?

CVE-2026-86175 is a high-severity vulnerability in netbox-community netbox, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NetBox through 4.7.0 fails to redact sensitive data source backend credentials in REST and GraphQL API responses. Authenticated users with only view permission can retrieve plaintext passwords and secret keys for Git and Amazon S3 backends through API endpoints, gaining unauthorized access to external repositories and storage buckets.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-86175 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86175 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86175 is a high-severity vulnerability in netbox-community netbox, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86175 exists.

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

## Sources

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

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