Vulnerability in @actual-app/sync-server (CVE-2026-49229)
Summary
Vulnerability in @actual-app/sync-server (CVE-2026-49229). Confidential information can be exposed externally. Exploitable via PATCH /admin/users. Mitigation: upgrade to 26.6.0 or later.
Original description
The description as published by the source.
Actual is a local-first personal finance app. Prior to 26.6.0, in OpenID multi-user mode, disabling a user only blocks future OpenID login for that identity, while existing Actual session tokens for the disabled user remain valid. The shared session validation path accepts any existing token row that has not expired without checking whether the associated user is still enabled, allowing a disabled user to continue calling authenticated server endpoints. This issue is fixed in version 26.6.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49229 has been found in @actual-app/sync-server.
Attackers can target a specific entry point like PATCH /admin/users over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.3/10.
What to do: upgrade @actual-app/sync-server to 26.6.0 or later.
If unsure, ask your IT team or search "@actual-app/sync-server CVE-2026-49229" on the vendor's site.
CVE-2026-49229 (@actual-app/sync-server) — CWE-613 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /admin/users / validateSessionMiddleware / never / validateSession
Patched: 26.6.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-613) exists in @actual-app/sync-server. Attackers reach the vulnerable code path via PATCH /admin/users.
Check the vendor advisory for the affected versions of @actual-app/sync-server. Attack surface: PATCH /admin/users / validateSessionMiddleware / never / validateSession.
Severity: High (CVSS 8.3/10). Confidential information can be exposed externally.
Update to 26.6.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PATCH /admin/users requests with malformed payloads or SQL meta-characters. Run grep -r '@actual-app/sync-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@actual-app/sync-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@actual-app/sync-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PATCH /admin/users' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /admin/usersへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @actual-app/sync-server to 26.6.0ステージング環境で 26.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PATCH /admin/users on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com