https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-19T04:17:02.554165+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-273973 EUVD-2026-273973 2026-10-19T04:17:02.557411+00:00 EUVD-2026-273973 https://cve.radiocsirt.org/vuln/fkie_cve-2026-27638 fkie_cve-2026-27638 2026-10-19T04:17:02.557449+00:00

Actual is a local-first personal finance tool. Prior to version 26.2.1, in multi-user mode (OpenID), the sync API endpoints (`/sync/*`) don't verify that the authenticated user owns or has access to the file being operated on. Any authenticated user can read, modify, and overwrite any other user's budget files by providing their file ID. Version 26.2.1 patches the issue.

 https://cve.radiocsirt.org/vuln/ghsa-qmjj-p7m9-wjrv GHSA-qmjj-p7m9-wjrv — @actual-app/sync-server: Missing authorization in sync endpoints allows cross-user budget file access in multi-user mode 2026-10-19T04:17:02.557493+00:00

Affected: npm: @actual-app/sync-server

In multi-user mode (OpenID), the sync API endpoints (`/sync/*`) don't verify that the authenticated user owns or has access to the file being operated on. Any authenticated user can read, modify, and overwrite any other user's budget files by providing their file ID.

## Affected Code

File: `packages/sync-server/src/app-sync.ts`

The `validateSessionMiddleware` on line 31 confirms the user is authenticated, but individual endpoints only check that the file *exists* (via `verifyFileExists`), never that the requesting user *owns* or *has access to* the file.

Compare with `POST /sync/delete-user-file` (lines 394-430) which correctly checks: ```js const isOwner = file.owner === userId; const isServerAdmin = isAdmin(userId); if (!isOwner && !isServerAdmin) { ... } ```

This check is missing from all other endpoints.

## Affected Endpoints

- `GET /sync/download-user-file` - download any budget file - `POST /sync/upload-user-file` - overwrite any budget file - `POST /sync/sync` - read/write sync messages of any file - `POST /sync/user-get-key` - read encryption key info - `POST /sync/user-create-key` - change encryption key - `POST /sync/reset-user-file` - reset sync state - `POST /sync/update-user-filename` - rename file - `GET /sync/get-user-file-info` - read file metadata

## PoC

Setup: Two users (Alice, Bob) authenticated via OpenID on the same Actual server. Alice has a budget with fileId `abc-123`.

Bob downloads Alice's budget: ```bash curl -X GET 'https://actual.example…