Security readout for executives and security teams
Plain-English summary
Microsoft UFO can let an authenticated peer impersonate a higher-privilege controller and redirect tasks to another connected device. The business risk is unauthorized automation activity across devices where UFO is deployed, because confidentiality, integrity, and availability are all rated high in CVSS.
Executive priority
Treat as a high-priority remediation item for any environment using UFO automation. Prioritize systems controlling sensitive devices, production workflows, or privileged automation because compromise could cross from one authenticated peer to another.
Technical view
In Microsoft UFO 3.0.1-4-ge2626659, the WebSocket control plane trusts role, target, and identity fields supplied in client messages. The registry also permits duplicate client_id registration, allowing live client state to be overwritten. This enables authenticated role and identity spoofing leading to peer task hijacking.
Likely exposure
Exposure appears limited to organizations running Microsoft UFO 3.0.1-4-ge2626659 with authenticated clients able to reach the WebSocket control plane. The source bundle does not identify other affected versions, hosted services, or downstream products.
Exploitation context
The source bundle marks KEV as false and provides no evidence of active exploitation. Abuse requires authenticated WebSocket access using the shared server token, but the reported privilege boundary failure makes impact high once that access exists.
Researcher notes
Evidence is limited to the CVE record and GitHub advisory reference. The key conditions are authenticated WebSocket access, shared token possession, trusted client-supplied role fields, and duplicate identity registration. No public exploit status or definitive patch details are included in the supplied sources.
Mitigation direction
- Check Microsoft/GitHub advisory guidance for fixed versions or vendor-recommended remediation.
- Restrict UFO WebSocket control-plane access to trusted networks and clients only.
- Rotate the shared server token if unauthorized client access is suspected.
- Monitor for duplicate client_id registration and unexpected role changes.
- Reduce privileges of automation tasks until remediation is confirmed.
Validation and detection
- Inventory UFO deployments and confirm whether 3.0.1-4-ge2626659 is present.
- Review WebSocket access paths and confirm only trusted clients can connect.
- Inspect logs for duplicate client_id registration or unexpected client_type values.
- Verify server-side authorization binds role and identity to the connection, not message fields.
- Confirm task dispatch cannot target peers without the registered role permitting it.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Open ATT&CK lookupCWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Open ATT&CK lookupCWE-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.
Open ATT&CK lookupCredential and access behavior lookup
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.
Open ATT&CK lookupCVE-2026-46414 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/microsoft/UFO/security/advisories/GHSA-qgx6-cvhg-jw7pCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.