CVE-2026-49229 Actual: Disabled OpenID users keep access through existing session tokens
Disabled OpenID users retain access via valid session tokens, bypassing account deactivation controls in Actual.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-49229?
CVE-2026-49229 is a high-severity authentication bypass vulnerability in actualbudget actual, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-613
Which versions are affected by CVE-2026-49229?
2 open source packages ship an affected version, including @actual-app/sync-server.
| Package | Affected | Fixed in |
|---|---|---|
@actual-app/sync-server npm | All versions | 26.6.0 |
@actual-app/sync-server npm | All versions | 26.6.0 |
How do I fix CVE-2026-49229?
Upgrade @actual-app/sync-server to 26.6.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-49229 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49229 exists.
Sources
Also known as GHSA-cq9c-6w48-qmfg.