Evidence record / omp

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-omp-ida-pro-became-agent-operable-owner-only-windows-daemons-require-closing-old-sessions

IDA Pro became agent-operable; owner-only Windows daemons require closing old sessions. Agents can open binaries, change an IDA database and execute Python in persistent project-shared hosts. ida.enabled defaults true and exposes the tool when a compatible local IDA install is found. list is read tier, exec is exec tier, other actions write; default yolo permits them without an ordinary prompt. v18.10.0 made local IPC owner-only across platforms, including Windows pipes. Old Windows daemons are not reused by the new release. This does not establish an earlier cross-user exploit.

Channel: tagged-release. Half: both. Date: 2026-09-25 (v18.3.1); 2026-10-12 (v18.10.0).

Operator consequence: Decide whether agents should operate your IDA installation: disable ida.enabled or prompt tools.approval.ida. Upgrade Windows hosts and close older OMP sessions; replacing the binary does not retrofit running older daemons.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-omp-ida-pro-became-agent-operable-owner-only-windows-daemons-require-closing-old-sessions

Profile citations

  • omp / claim / ida-and-windows-daemons

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact