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.
CVE-2026-49229
This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- EG Score
- 8.3(medium)
- EG Risk
- 53(Track*)EG Risk 53/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity83% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS
- 36.0%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
July 9, 2026
Advisory Details (3)
Auto-updated Jul 7, 2026Disabled OpenID users keep access through existing session tokens · Advisory · actualbudget/actual · GitHub
https://github.com/actualbudget/actual/security/advisories/GHSA-cq9c-6w48-qmfgv26.6.0
Patch available: actualbudget/actual v26.6.0
https://github.com/actualbudget/actual/releases/tag/v26.6.0commit c8cb8a223a4f (actualbudget/actual)
Fix landed in actualbudget/actual commit c8cb8a223a4f — awaiting tagged release
https://github.com/actualbudget/actual/commit/c8cb8a223a4faf1c2e1dcb0795a79a93f7b19e80Vendor Advisories for CVE-2026-49229(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @actual-app/sync-server | — | 26.6.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-06-22 23:30 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-613
Frequently asked(5)
What is CVE-2026-49229?
When was CVE-2026-49229 disclosed?
Is CVE-2026-49229 actively exploited?
What is the CVSS score of CVE-2026-49229?
How do I remediate CVE-2026-49229?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49229
Is Your Infrastructure Affected by CVE-2026-49229?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.