dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-46544

MEDIUM · 5.3 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 →
59/100
Remediation priority · Elevated
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 accepts client-supplied session_id values in WebSocket task messages and reuses an existing in-memory session object if that session_id already exists. If a prior session has completed and remains in memory with populated results, a different authenticated client can send a new TASK message using the same session_id. The server re-enters the existing session object and sends the stale stored result to the new requester through the normal send_task_end() callback path. This is an authenticated cross-client stale result replay issue. The issue requires that the attacker knows or can predict a live or recently completed session_id.

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 framework accepts client-supplied session_id values in WebSocket messages and reuses existing in-memory session objects when the same session_id is presented. If a prior session completed but remains in memory with results, an authenticated attacker knowing the session_id can send a new TASK message and receive stale cached results intended for the original client, enabling cross-client result replay.

MitigationImplement server-generated session IDs with proper validation, clear session data immediately after task completion, or invalidate sessions after use to prevent stale result replay.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 framework installation
    Search for UFO-related packages, modules, or services in your environment. Check for 'ufo', 'microsoft ufo', or related process/service names running on the system.
    Affected if The Microsoft UFO framework is present and running in your environment.
  2. Verify WebSocket endpoint exposure
    Review your UFO framework configuration for exposed WebSocket endpoints. Check network listener configuration or proxy settings for WebSocket upgrade paths (ws:// or wss:// URLs handling session-based communications).
    Affected if WebSocket endpoints are exposed and accepting connections with session_id parameters.
  3. Inspect session ID generation mechanism
    Examine the UFO framework source code or configuration for how session_id values are handled. Determine if session IDs are server-generated (secure) or client-supplied (vulnerable). Look for session ID validation logic in the WebSocket message handler.
    Affected if Session IDs are accepted from clients without server-side generation or validation.
  4. Check session persistence configuration
    Review session management settings to determine how long session objects remain in memory after task completion. Look for session timeout, cache TTL, or cleanup interval configurations.
    Affected if Sessions or cached results remain in memory after the original task completes.
  5. Test for result replay vulnerability
    If you have an authenticated session, complete a task to generate results, note the session_id, then send a new TASK message with the same session_id from a different connection. Observe if stale results are returned.
    Affected if The same session_id from different connections returns cached results from a prior completed session.

Your environment is affected if Microsoft UFO framework is running with WebSocket endpoints that accept client-supplied session IDs and retain session objects in memory after task completion, allowing cross-client result replay.

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

Implement server-generated session IDs with proper validation, clear session data immediately after task completion, or invalidate sessions after use to prevent stale result replay.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46544 — 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-46544 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