GCVE-110-VULN-PYPI-2026-000614

aimarket-treasury 0.1.0 and 0.1.1 require the X-Treasury-Client token on the routes that decide and move money (POST /authorize, /deposit, /vault/fund, /vault/reserve, /vault/top-up and /explain; service._require_client) only in production mode. With TREASURY_CLIENT_TOKEN unset and production mode off, which is the default, the check returns and any caller is served. The service binds 0.0.0.0 (treasury.service.main). A caller can obtain a treasury-signed authorization decision for a finding it submits, add budget to the vault, reserve funds against a finding and request a top-up, which corrupts the vault's balance and journal. Settlement is simulated in this release, and an authorization still needs a valid scanner signature and the external-verifier quorum. Fixed in 0.1.3: without a token those routes answer only a caller on the machine's own user (loopback peer, loopback Host, no forwarding header and, on Linux, a socket owned by the server's user). Affects 0.1.0 and 0.1.1.