CVE-2026-49229: actualbudget actual · Insufficient Session Expiration
Affects actualbudget actualSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 26.6.0 soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.6.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade actual and actualbudget/actual to 26.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| actualbudgetactual | Affected
| Fixed in
|
GitHubactualbudget/actualpkg:github/actualbudget/actualOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Actual version 26.6.0 or later, where this vulnerability is fixed by properly invalidating session tokens of disabled users. Since this is a local app and not a cloud service, users must apply the update themselves. Patch status is confirmed fixed in 26.6.0.
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.