Classic298 920b655f46 Gate scheduled automations and fail closed on per-model access for non-user roles (#26047) ...

Two lifecycle/authorization gaps let a deactivated (pending) account keep acting:

1. The background automation scheduler (execute_automation) rehydrated the owner by ID and
   dispatched the chat pipeline without re-checking the owner. A user later set to pending,
   or one whose features.automations permission was revoked, kept running scheduled
   automations on the operator's provider credentials, even though the HTTP create/update/run
   routes already gate on get_verified_user + features.automations. Re-gate the rehydrated
   owner before dispatch: require role user/admin and, for non-admins, the features.automations
   permission; otherwise record an error and skip the run.

2. check_model_access enforced per-model ACLs only for exactly role == 'user', so any other
   non-admin role (a pending principal) fell through and was granted access. Enforce for every
   non-admin role (admins still bypass), so the check fails closed (CWE-862, CWE-863).

Co-authored-by: rexpository <30176934+rexpository@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-16 22:45:27 +02:00

..

__init__.py

Gate scheduled automations and fail closed on per-model access for non-user roles (#26047)

2026-06-16 22:45:27 +02:00

files.py

fix: respect access_type in shared-chat file authorization branch (#24755)

2026-05-19 22:09:56 +04:00

folders.py

refac

2026-06-15 23:34:24 +02:00