Jet Admin tenant isolation failure

Answer in brief

CVE-2026-75932 records a Unknown severity vulnerability in Jet Admin tenant isolation failure. The current sources do not mark it as known exploited. The current feed maps Jet Admin/Jet Admin (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 21, 2026Updated Aug 21, 2026Source checked Aug 21, 2026First seen by HOL Aug 21, 2026Material review Aug 21, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Jet Admin/Jet Admin (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Jet Admin/Jet Admingeneric	>=0 <*	*

Recommended response

Check inventory. Check lockfiles and deployed manifests for Jet Admin/Jet Admin.
Review the reported fix. Update Jet Admin/Jet Admin to * if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 21, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.