Summary
Actual Sync Server: CORS Proxy GitHub API Allowlist Prefix Bypass Leaks Private Repositories Through the Server GitHub Token
Impact
- Any authenticated Actual user can use the server's GitHub token against prefix-matched repositories outside the plugin allowlist.
- Private source code, repository metadata, release data, deployment files, and accidentally committed secrets can be exposed.
- If the token has broad organization or user repository read permissions, a public allowlisted plugin repo can become a stepping stone to multiple private repos sharing the same name prefix.
- Exposed repository secrets or deployment material may enable follow-on compromise of production infrastructure or supply-chain release assets.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
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-57449? CVE-2026-57449 is a high-severity incorrect authorization vulnerability in @actual-app/sync-server (npm), affecting versions <= 26.6.0. It is fixed in 26.7.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of @actual-app/sync-server are affected by CVE-2026-57449? @actual-app/sync-server (npm) versions <= 26.6.0 is affected.
- Is there a fix for CVE-2026-57449? Yes. CVE-2026-57449 is fixed in 26.7.0. Upgrade to this version or later.
- Is CVE-2026-57449 exploitable, and should I be worried? Whether CVE-2026-57449 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-57449 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-57449? Upgrade
@actual-app/sync-serverto 26.7.0 or later.