CVE-2026-46700: CWE-285: Improper Authorization in actualbudget actual
Actual is a local-first personal finance tool. Prior to 26.6.0, the GET /secret/:name endpoint in @actual-app/sync-server checks only that the caller has a valid session and does not verify the caller is an admin, while the sibling POST /secret/ handler enforces an admin check in OpenID mode. 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, including simplefin_accessKey, pluggyai_clientSecret, pluggyai_itemIds, and the gocardless secrets. This issue is fixed in version 26.6.0.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-46700) in Actualbudget's Actual product affects versions prior to 26.6.0. The GET /secret/:name endpoint in the @actual-app/sync-server component only checks for a valid session but fails to enforce admin authorization. Consequently, authenticated non-admin BASIC users in OpenID multi-user environments can enumerate and access secrets related to admin-managed bank-sync integrations, including keys and client secrets. The sibling POST /secret/ endpoint properly enforces admin checks in OpenID mode, but the GET endpoint does not. This improper authorization issue is resolved in version 26.6.0.
Potential Impact
An authenticated non-admin user can access sensitive secret information related to admin-managed bank-sync integrations, potentially exposing credentials such as simplefin_accessKey, pluggyai_clientSecret, pluggyai_itemIds, and gocardless secrets. This exposure could lead to unauthorized disclosure of sensitive configuration data. The CVSS score is 4.3 (medium severity), reflecting limited impact on confidentiality without integrity or availability effects.
Mitigation Recommendations
Upgrade to Actual version 26.6.0 or later, where the improper authorization vulnerability in the GET /secret/:name endpoint is fixed. No other mitigations are indicated by the vendor advisory.
CVE-2026-46700: CWE-285: Improper Authorization in actualbudget actual
Description
Actual is a local-first personal finance tool. Prior to 26.6.0, the GET /secret/:name endpoint in @actual-app/sync-server checks only that the caller has a valid session and does not verify the caller is an admin, while the sibling POST /secret/ handler enforces an admin check in OpenID mode. 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, including simplefin_accessKey, pluggyai_clientSecret, pluggyai_itemIds, and the gocardless secrets. This issue is fixed in version 26.6.0.
CVSS v3.1
Score 4.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-46700) in Actualbudget's Actual product affects versions prior to 26.6.0. The GET /secret/:name endpoint in the @actual-app/sync-server component only checks for a valid session but fails to enforce admin authorization. Consequently, authenticated non-admin BASIC users in OpenID multi-user environments can enumerate and access secrets related to admin-managed bank-sync integrations, including keys and client secrets. The sibling POST /secret/ endpoint properly enforces admin checks in OpenID mode, but the GET endpoint does not. This improper authorization issue is resolved in version 26.6.0.
Potential Impact
An authenticated non-admin user can access sensitive secret information related to admin-managed bank-sync integrations, potentially exposing credentials such as simplefin_accessKey, pluggyai_clientSecret, pluggyai_itemIds, and gocardless secrets. This exposure could lead to unauthorized disclosure of sensitive configuration data. The CVSS score is 4.3 (medium severity), reflecting limited impact on confidentiality without integrity or availability effects.
Mitigation Recommendations
Upgrade to Actual version 26.6.0 or later, where the improper authorization vulnerability in the GET /secret/:name endpoint is fixed. No other mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-15T23:26:58.308Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4d6893c9d9e3dbe3d54567
Added to database: 07/07/2026, 20:58:59 UTC
Last enriched: 07/15/2026, 12:11:48 UTC
Last updated: 08/19/2026, 22:52:13 UTC
Views: 67
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.