Vulnerability Description
Actual is a local-first personal finance tool. Prior to 26.7.0, Actual Sync Server's CORS proxy is intended to let authenticated users fetch resources only from repositories listed in the official plugin allowlist. When `ACTUAL_GITHUB_TOKEN` is configured, the proxy automatically attaches the server's GitHub token to GitHub requests. The GitHub API allowlist check uses a raw `startsWith()` prefix test for `/repos/{owner}/{repo}` without requiring a path boundary after the repository name. If an allowlisted public plugin repository is `https://github.com/acme/plugin`, the proxy also accepts GitHub API URLs. Those URLs are outside the allowlisted repository but still pass because their API path starts with `/repos/acme/plugin`. The proxy then forwards the request with the server's `ACTUAL_GITHUB_TOKEN`, allowing any authenticated Actual user to read private GitHub resources reachable by that token. Version 26.7.0 fixes the issue.
Related Weaknesses (CWE)
References
- https://github.com/actualbudget/actual/security/advisories/GHSA-m62c-5q34-f3cf
- https://github.com/actualbudget/actual/security/advisories/GHSA-m62c-5q34-f3cf
FAQ
What is CVE-2026-57449?
CVE-2026-57449 is a documented vulnerability. Actual is a local-first personal finance tool. Prior to 26.7.0, Actual Sync Server's CORS proxy is intended to let authenticated users fetch resources only from repositories listed in the official plu...
How severe is CVE-2026-57449?
CVSS scoring is not yet available for CVE-2026-57449. Check NVD for updates.
Is there a patch for CVE-2026-57449?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.