{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-46538 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46538 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46538 is a medium-severity missing authorization vulnerability in microsoft UFO, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46538 and fix it if it is affected.\n\nWhat it is: CVE-2026-46538 is a medium-severity missing authorization vulnerability in microsoft UFO, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46538 in the wild and no public exploit code.\n\nAffected product: microsoft UFO. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46538/ (Markdown: https://insights.sbomify.com/CVE-2026-46538/index.md)","id":"CVE-2026-46538","markdown":"https://insights.sbomify.com/CVE-2026-46538/index.md","name":"CVE-2026-46538","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft UFO framework","requires_auth":"low_privilege","summary":"An authenticated peer can inject forged task results into Microsoft UFO by spoofing session IDs, potentially compromising automation workflows.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"Microsoft UFO open-source framework for intelligent automation across devices and platforms. In 3.0.1-4-ge2626659, Microsoft UFO's constellation client tracks pending task responses by session_id only and does not verify that a TASK_END message came from the device that originally received the task. When the constellation sends a task to a target device, it records a pending Future under a session key. The pending task record stores the expected device ID, but the completion path ignores that binding. If another authenticated peer device sends a forged TASK_END with the same session_id, the constellation accepts the response and completes the victim device's pending Future with attacker-controlled result data. This is an authenticated cross-device task-result injection issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Microsoft UFO accepts cross-device TASK_END messages by session_id only, allowing peer task-result injection","id":"CVE-2026-46538","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"nimiq-primitives: BlockInclusionProof interlink issue when hops are empty","id":"CVE-2026-46539"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-46537"},"products":["UFO"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["microsoft"]},"summary":"An authenticated peer can inject forged task results into Microsoft UFO by spoofing session IDs, potentially compromising automation workflows.","url":"https://insights.sbomify.com/CVE-2026-46538/"}