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.
References7
- github.com/microsoft/UFO/commit/f31fb5ef7d07b7825a03fe34b88f1f2…
- github.com/microsoft/UFO/releases/tag/v3.0.9
- github.com/microsoft/UFO/security/advisories/GHSA-3pgm-xw75-hq27
- github.com/microsoft/UFO/security/advisories/GHSA-3pgm-xw75-hq27
- github.com/microsoft/UFO/security/advisories/GHSA-3pgm-xw75-hq27
- github.com/microsoft/UFO/security/advisories/GHSA-3pgm-xw75-hq27
- github.com/microsoft/UFO/security/advisories/GHSA-3pgm-xw75-hq27
Metrics
- CVSS 3.1
-
6.4
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N - EPSS — exploit probability
- 1% percentile: 45 · as of 10 November 2026
- CWE
- CWE-918
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.