EUVD-2026-335306

fkie_cve-2026-49229

Actual is a local-first personal finance app. Prior to 26.6.0, in OpenID multi-user mode, disabling a user only blocks future OpenID login for that identity, while existing Actual session tokens for the disabled user remain valid. The shared session validation path accepts any existing token row that has not expired without checking whether the associated user is still enabled, allowing a disabled user to continue calling authenticated server endpoints. This issue is fixed in version 26.6.0.

GHSA-cq9c-6w48-qmfg — @actual-app/sync-server: Disabled OpenID users keep access through existing session tokens

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

### Summary

In OpenID multi-user mode, disabling a user only blocks future OpenID login for that identity. Existing Actual session tokens for the disabled user remain valid, so the user can continue calling authenticated server endpoints after an administrator has disabled the account.

### Details

The disabled-user check is present during OpenID login finalization. Existing users are only accepted when the matching row has `enabled = 1`, and a disabled row causes the OpenID grant to fail before a new session token is created.

```ts // packages/sync-server/src/accounts/openid.ts:284-291 const { id: userIdFromDb, display_name: displayName } = accountDb.first( 'SELECT id, display_name FROM users WHERE user_name = ? and enabled = 1', [identity], ) || {};

if (userIdFromDb == null) { throw new Error('openid-grant-failed'); } ```

The shared session validation path does not perform the same enabled-user check. It accepts any existing token row that has not expired, then returns the session object to every route protected by `validateSessionMiddleware`.

```ts // packages/sync-server/src/util/validate-user.ts:10-41 export function validateSession(req: Request, res: Response) { let { token } = req.body || {}; if (!token) { token = req.headers['x-actual-token']; }

const session = getSession(token); ... return session; } ```

This means account disablement and session authorization diverge:

```text OpenID login path: users.enabled must be 1 Existing…

Most recent entries from all

EUVD-2026-335306

fkie_cve-2026-49229

GHSA-cq9c-6w48-qmfg — @actual-app/sync-server: Disabled OpenID users keep access through existing session tokens