actualbudget actual up to 26.2.0 Sync API Endpoint /sync/ authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in actualbudget actual up to 26.2.0. This impacts an unknown function of the file /sync/ of the component Sync API Endpoint. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-27638. Local access is required to approach this attack. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in actualbudget actual up to 26.2.0. It has been rated as problematic. This issue affects some unknown processing of the file /sync/ of the component Sync API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is integrity, and availability. The summary by CVE is:
Actual is a local-first personal finance tool. Prior to version 26.2.1, in multi-user mode (OpenID), the sync API endpoints (`/sync/*`) don't verify that the authenticated user owns or has access to the file being operated on. Any authenticated user can read, modify, and overwrite any other user's budget files by providing their file ID. Version 26.2.1 patches the issue.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-27638 since 02/20/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 26.2.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 9966c024cb75f57943193cac8e42f401efed9d08 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-8905). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: actual 26.2.1
Patch: 9966c024cb75f57943193cac8e42f401efed9d08
Timeline
02/20/2026 CVE reserved02/27/2026 Advisory disclosed
02/27/2026 VulDB entry created
03/01/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-qmjj-p7m9-wjrv
Status: Confirmed
CVE: CVE-2026-27638 (🔒)
GCVE (CVE): GCVE-0-2026-27638
GCVE (VulDB): GCVE-100-348137
EUVD: 🔒
Entry
Created: 02/27/2026 08:05Updated: 03/01/2026 16:10
Changes: 02/27/2026 08:05 (71), 03/01/2026 00:15 (1), 03/01/2026 16:10 (13)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.