# CVE-2026-75932: Jet Admin tenant isolation failure

> Attackers can hijack custom domains to steal OAuth credentials and access victim data due to tenant isolation failures.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-cm72-j98h-q99g

## What is CVE-2026-75932?

CVE-2026-75932 is a critical missing authorization vulnerability in Jet Admin, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jet Admin allows an attacker to create a malicious app and connect it to a target user's custom domain, edit the authentication configuration, and reroute traffic to the attacker-controlled app. Once connected to the target domain, the attacker's workspace is populated with the victim's OAuth Client ID and Client Secret if the victim is using an OAuth provider.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75932 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75932 is a critical missing authorization vulnerability in Jet Admin, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75932 in the wild and no public exploit code.

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

## Sources

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

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