CVE-2026-46700 is a medium-severity security vulnerability in @actual-app/sync-server (npm), affecting versions < 26.6.0. It is fixed in 26.6.0.
Summary In @actual-app/sync-server, the GET /secret/:name endpoint (app-secrets.js:53) checks only that the caller has a valid session, it does not verify the caller is an admin. The sibling POST /secret/ handler does enforce an admin check in OpenID mode, exposing an authorization asymmetry. Any authenticated non-admin (BASIC) user in OpenID multi-user deployments can probe the secrets store and learn which admin-managed bank-sync integrations have been configured (existence, not values). This includes integration credentials that are not otherwise observable to non-admins, such as simplefinaccessKey, pluggyaiclientSecret, pluggyaiitemIds, and the gocardless secrets. Details packages/sync-server/src/app-secrets.js mounts validateSessionMiddleware at the router level (line 15), so all handlers inherit only "must be authenticated." The POST handler then explicitly upgrades to an admin check when the active auth method is openid: The sibling GET handler skips both the method check and the admin check entirely: The intent, visible from the POST handler's "You have to be admin to set secrets", is that this store holds admin-managed credentials. The valid secret names enumerated in services/secrets-service.js (SecretName) are: gocardlesssecretId, gocardlesssecretKey, simplefintoken, simplefinaccessKey, pluggyaiclientId, pluggyaiclientSecret, pluggyaiitemIds. In OpenID mode, BASIC users obtain valid sessions through packages/sync-server/src/accounts/openid.ts:264-274, either auto-created (userCreationMode=login) or pre-provisioned by the admin (userCreationMode=manual). With that BASIC session token they can hit GET /secret/:name and distinguish 204 (configured) from 404 (missing), enumerating each admin-managed secret name. Some signals (simplefintoken existence, pluggyaiclientId existence) are already coarsely observable via the unauthenticated bank-sync status endpoints (app-simplefin.js:18, app-pluggyai.js:18); the rest (simplefinaccessKey, pluggyaiclientSecret, pluggyaiitemIds, both gocardless secrets) are not otherwise probeable. This is structurally identical to the previously reported missing-admin-check on GET /admin/users/ (app-admin.js:28): a POST sibling enforces admin authorization while the GET sibling omits it. PoC Pre-requisites: Server is configured for OpenID multi-user mode (ACTUALOPENIDENFORCE=true or auth method is openid). An admin has configured one or more bank-sync integrations. The attacker is any authenticated BASIC user (auto-created via userCreationMode=login, or admin-provisioned in the default manual mode). Step 1, capture a BASIC user's session token in $TOKEN (standard OpenID login flow, no admin role required). Step 2, probe each admin-managed secret name: Step 3, confirm the asymmetry by attempting to write a secret (correctly rejected for non-admins): The POST returns 403 not-admin; the GET returns 204/404 unauthenticated-against-role. Impact A non-admin authenticated user in OpenID multi-user mode can enumerate which admin-managed bank-sync integrations the deployment uses. This reveals whether GoCardless, SimpleFIN, and/or Pluggy AI are configured, and which auxiliary credentials the admin has set (e.g. simplefinaccessKey, pluggyaiclientSecret, pluggyaiitemIds), none of which are otherwise observable to non-admins. The disclosure is existence-only; secret values are not returned. Impact is limited to recon useful for targeted follow-on attacks (e.g. credential phishing, picking which integration to attack on a separate vulnerability). No integrity or availability impact. Recommended Fix Mirror the POST handler's admin gate on the GET handler. Minimal patch in packages/sync-server/src/app-secrets.js: Consider factoring the method-lookup + admin-check into a shared helper used by both POST and GET to prevent the same asymmetry from recurring. Also consider restricting :name to the SecretName enum so unrelated probing is rejected up front.
CVE-2026-46700 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (26.6.0). Upgrading removes the vulnerable code path.
npm
@actual-app/sync-server (< 26.6.0)@actual-app/sync-server → 26.6.0 (npm)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-46700 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-46700 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-46700 in your environment →Upgrade @actual-app/sync-server to 26.6.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-46700 is a medium-severity security vulnerability in @actual-app/sync-server (npm), affecting versions < 26.6.0. It is fixed in 26.6.0.
CVE-2026-46700 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
@actual-app/sync-server (npm) versions < 26.6.0 is affected.
Yes. CVE-2026-46700 is fixed in 26.6.0. Upgrade to this version or later.
Whether CVE-2026-46700 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade @actual-app/sync-server to 26.6.0 or later.