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.
Security readout for executives and security teams
Plain-English summary
A flaw in Jet Admin may let an unauthenticated attacker attach a malicious application to another customer’s custom domain. The attacker could redirect that domain’s traffic and, when OAuth is configured, receive the victim’s OAuth client ID and secret. This creates risks of service disruption, credential exposure, and unauthorized access through trusted domains.
Executive priority
Treat this as an immediate exposure-assessment priority. Organizations using Jet Admin custom domains should urgently verify tenant ownership and investigate OAuth credential exposure. Escalate to incident response if associations changed unexpectedly or OAuth activity is suspicious. Remediation specifics remain incomplete in the supplied sources, so obtain current vendor guidance before declaring the risk resolved.
Technical view
CVE-2026-75932 is a tenant-isolation and missing-authorization-control failure, classified as CWE-862. The reported path permits malicious app creation, unauthorized custom-domain association, authentication-configuration changes, traffic rerouting, and disclosure of OAuth client credentials. CVSS 4.0 is 9.2, reflecting remote, low-complexity, unauthenticated exploitation with serious availability and downstream confidentiality impact.
Likely exposure
Exposure is most likely for organizations using Jet Admin with custom domains. Impact increases when those applications use OAuth providers because client credentials may populate the attacker’s workspace. The supplied records do not clearly identify affected versions, deployment boundaries, or whether every custom-domain configuration is vulnerable.
Exploitation context
The described attack is remote, low complexity, requires no privileges or user interaction, and abuses cross-tenant domain association. The source bundle marks this CVE as absent from KEV, and no supplied source confirms active exploitation. Absence from KEV does not establish that exploitation has never occurred.
Researcher notes
The record supports an authorization failure affecting tenant isolation, custom-domain binding, authentication configuration, and OAuth secret confidentiality. Version information is not meaningful beyond an entry of “0” with unknown default status. No patch, fixed version, vendor mitigation, proof of concept, or exploitation evidence is included. Validation should emphasize control-plane history and downstream OAuth telemetry without testing against third-party tenants.
Mitigation direction
Check Jet Admin’s current security guidance for an official fix or configuration mitigation.
Inventory Jet Admin custom domains and confirm each remains associated with the authorized workspace.
Restrict or suspend affected custom-domain integrations if Jet Admin recommends doing so.
Rotate potentially exposed OAuth client secrets after securing the domain association.
Review OAuth provider permissions and reduce excessive application privileges.
Validation and detection
Identify all Jet Admin applications using custom domains or OAuth authentication.
Verify custom-domain ownership and workspace association through trusted administrative records.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.