# CVE-2026-105790: Microsoft UFO: Authenticated Galaxy device registration can bypass WebSocket SSRF IP pinning via redirects


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-3pgm-xw75-hq27

## What is CVE-2026-105790?

CVE-2026-105790 is a medium-severity vulnerability in microsoft UFO, published on 6 Oct 2026. 

### Official description

Microsoft UFO is an open-source framework for intelligent automation across devices and platforms. Prior to 3.0.9, authenticated device registration through /api/devices can supply a permitted attacker-controlled WebSocket endpoint while aip/transport/websocket.py applies pinned_addresses only to the initial destination. The pinned websockets.connect() client follows cross-origin redirects and opens a new TCP connection before Galaxy performs its post-handshake peer-IP validation, allowing WebSocket upgrade requests to internal hosts reachable from the server. The confirmed impact is the internal connection and handshake request, and does not establish arbitrary HTTP methods, response-body disclosure, a completed AIP session, or cloud metadata access. This issue is fixed in version 3.0.9.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-105790?


## How do I fix CVE-2026-105790?

No fix has been published for CVE-2026-105790 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105790 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105790 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105790 and fix it if it is affected.

What it is: CVE-2026-105790 is a medium-severity vulnerability in microsoft UFO, published on 6 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105790 exists.

Affected product: microsoft UFO. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105790/ (Markdown: https://insights.sbomify.com/CVE-2026-105790/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105790
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105790
- OSV: https://osv.dev/vulnerability/CVE-2026-105790

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105790/
Summaries are generated and may contain mistakes; the official description above is the record.