What happened?
Right now, TablePro scans for a free local port, releases it, and only then launches ssh -L ....
Another local process can bind that port in the gap between the availability check and the actual ssh bind, which is a potential vulnerability and attack surface.
Environment
0.15.0 / macOS 26.3.1 / Apple Silicon
Screenshots / Logs
No response