Diego Rodrigues de Sa e Souza a47ce51d4c fix(api): classify /api/acp/agents as loopback-only (#7948) (#7966) ...

* fix(api): classify /api/acp/agents as loopback-only (#7948)

/api/acp/agents is spawn-capable (POST registers a client-chosen `binary`
via src/lib/acp/registry.ts; GET / POST {action:"refresh"} runs
detectInstalledAgents() -> execFileSync(probe.command, probe.args, { shell })
transitively) but was never added to LOCAL_ONLY_API_PREFIXES in
src/server/authz/routeGuard.ts, unlike every sibling spawn-capable route
(Hard Rules #15/#17). A leaked JWT via tunnel could reach the version-probe
execFileSync path.

Adds the prefix to the loopback gate plus a direct regression test
(tests/unit/route-guard-acp-agents-local-only.test.ts) and an assertion in
tests/unit/check-route-guard-membership.test.ts documenting why the existing
source-scan subcheck cannot catch this class of gap (the spawn call is
transitive via registry.ts, not in the route file itself).

* chore(quality): register route-guard-acp-agents-local-only test in stryker tap.testFiles

2026-07-21 09:03:31 -03:00

..

auth

Release v3.8.28 (#4053)

2026-06-17 19:26:32 -03:00

authz

fix(api): classify /api/acp/agents as loopback-only (#7948) (#7966)

2026-07-21 09:03:31 -03:00

cors

feat(api): add Vary: Accept-Encoding to token-authenticated /v1* responses (#6737) (#7217)

2026-07-17 10:39:58 -03:00

origin

Release v3.8.41 (#5327)

2026-06-29 16:51:03 -03:00

ws

fix(db): stop a 'latest' path segment from disabling backups and migrations (#7359)

2026-07-18 11:35:00 -03:00