dbcve.org
CWE-290Weakness · CWE-290

CVE-2026-46414

HIGH · 8.8 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft UFO open-source framework for intelligent automation across devices and platforms. In 3.0.1-4-ge2626659, Microsoft UFO's WebSocket control plane trusts client-supplied identity and role fields in task messages. A client connection can register as a normal device, but later send a TASK message claiming client_type="constellation" and target_id=<victim-device-id>. The server trusts the role and target values from the wire message rather than enforcing the role registered for that WebSocket connection. As a result, any authenticated WebSocket client with the shared server token can spoof the higher-privilege constellation role and dispatch attacker-controlled tasks to another connected device. The same client registry also allows duplicate client_id registration, overwriting an existing live client's stored websocket, role, and task protocol. This is an authenticated WebSocket role/identity spoofing issue leading to peer task hijacking.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Microsoft UFO's WebSocket control plane trusts client-supplied identity and role fields in TASK messages rather than enforcing the role registered during WebSocket handshake. An authenticated attacker with the shared server token can register as a normal device, then send a TASK message claiming client_type='constellation' to spoof higher-privilege roles and dispatch attacker-controlled tasks to victim devices. Additionally, the client registry permits duplicate client_id registration that overwrites existing live client sessions.

MitigationEnforce the role and identity established during WebSocket connection registration, reject client-supplied role/target fields in task messages, and prevent duplicate client_id registrations from overwriting active sessions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Microsoft UFO installation
    Search for UFO-related processes, services, or installed components. Check for 'ufo', 'Microsoft UFO', or 'UFO control plane' in running processes, services, or installed software listings.
    Affected if Microsoft UFO WebSocket control plane component is present and running on the system
  2. Determine UFO version
    Query the UFO service for its version information via --version flag, API endpoint, or configuration file metadata. Compare against any released patch versions.
    Affected if Running version lacks the fix for role validation in TASK messages
  3. Verify WebSocket registration behavior
    Inspect WebSocket handshake and client registration code or logs. Check if client_id, client_type, and role are taken solely from handshake registration or if TASK messages can override these fields.
    Affected if TASK messages are processed with client-supplied role/target fields instead of enforcing handshake-registered identity
  4. Detect duplicate client_id registration
    Review client registry logs or database. Attempt to register a second session with an existing client_id and observe whether it succeeds and overwrites the original session.
    Affected if Duplicate client_id registration succeeds and terminates or displaces existing active sessions
  5. Audit for spoofed TASK messages
    Review WebSocket message logs for TASK messages where client_type differs from the role registered at handshake time, especially client_type='constellation' claims from lower-privilege registered devices.
    Affected if TASK messages with mismatched or elevated client_type values are accepted and processed

The environment is affected if Microsoft UFO is running with a WebSocket control plane that accepts role/target fields from TASK messages rather than enforcing those established during handshake, and permits duplicate client_id registrations to overwrite live sessions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enforce the role and identity established during WebSocket connection registration, reject client-supplied role/target fields in task messages, and prevent duplicate client_id registrations from overwriting active sessions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46414 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data