Back to news
VAF 0.1.0a31: a code audit that checks its own findings
In VAF 0.1.0a31 the agent's web fetches no longer reach VAF itself, and a Nextcloud connected as localhost needs its network address.
0.1.0a31 is out. VAF reviews code changes for bugs, security holes and risky changes, and checks every finding against the code before reporting it. An invented finding is dropped, a doubtful one is listed apart. The coding sub-agent reviews its own work this way and fixes what it finds, in at most 50 rounds, switchable by an administrator. In the terminal, vaf audit run reviews any git repository with your configured model.
vaf updateOne security hole is closed:
- The agent's web fetches no longer reach VAF itself. On the computer VAF runs on, a request from that computer counts as you. A web page, a mail or the model could therefore make the agent read your contacts, the account list or the settings from VAF, or reach the cloud metadata service. Addresses on this computer and the cloud metadata service are now refused; only a remote MCP server an administrator registered may still run on this computer. Devices in your home network stay reachable, each such fetch is noted in the logs, and an administrator can switch that off with egress_allow_private_hosts. A page one account fetched is also no longer served from the cache to another account.
A Nextcloud running on the same computer and connected as localhost falls under this block. To keep using it, connect it again with its network address.