Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 20 October 2025.

Which products and versions are affected?

@actual-app/sync-server (npm) SEMVER:introduced=0,fixed=25.11.0.

Is there a fix for This vulnerability?

Yes. @actual-app/sync-server (npm): upgrade to 25.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked with local access, in a hosted service.

Check whether you run @actual-app/sync-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Actual Sync-server GoCardless service logging sensitive data

Severity: low · CVSS 3.1 · Published 2025-10-20

Actual's sync-server component logs sensitive banking data to standard output when integrating with GoCardless, a payment platform. Exposed information includes API bearer tokens, customer bank account numbers (IBANs), account holder names, and transaction details. Anyone with access to application logs or Docker containers can retrieve these credentials and personally identifiable information, risking unauthorized access to banking accounts and customer data breaches.

Technologies: @actual-app/sync-server (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 20 October 2025.
Which products and versions are affected?: @actual-app/sync-server (npm) SEMVER:introduced=0,fixed=25.11.0.
Is there a fix for This vulnerability?: Yes. @actual-app/sync-server (npm): upgrade to 25.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked with local access, in a hosted service.
Am I affected?: Check whether you run @actual-app/sync-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@actual-app/sync-server (npm): upgrade to 25.11.0 or later
```
npm install @actual-app/sync-server@25.11.0
```

Technical details

The GoCardless integration in Actual's sync-server uses console.log and console.debug to output API responses and error stack traces without filtering. The vulnerability stems from two code paths: (1) debug logging of complete GoCardless API account and transaction responses via console.debug in integration-bank.js, and (2) unhandled exception logging that dumps full error stack traces including HTTP headers containing Authorization bearer tokens in app-gocardless.js. Both vectors are reachable during normal operation (e.g., when calling GoCardless APIs or when upstream services return HTTP errors). The logged data flows to Docker logs and application log files, accessible to infrastructure operators and potentially exposed in centralized logging systems. Versions 25.10.0 and earlier are affected; patches available in 25.11.0 and later remove or redact sensitive data from logs.

Affected products

Actual Technologies Actual <= 25.10.0

Timeline

2025-10-18: disclosed
2025-11-00: patched: Fix released in version 25.11.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.