dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-43872

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Actual is an open-source personal finance application. Prior to version 26.5.0, several endpoints are affected by a path traversal vulnerability. Version 26.5.0 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Actual personal finance application versions prior to 26.5.0 contain a path traversal vulnerability affecting multiple endpoints, allowing attackers to access files outside the intended web root directory through specially crafted path inputs.

MitigationUpgrade to Actual version 26.5.0 or later, which contains the patch for this path traversal vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the installed Actual version
    Locate the Actual application installation directory and check the package.json, version file, or application metadata that contains the version number. If running as a service or container, use the appropriate command to retrieve the version (such as checking the Docker image tag, npm package version, or applicationAbout/info endpoint).
    Affected if The installed version is any release prior to 26.5.0 (for example, 26.4.0, 26.3.0, 26.x.y where x < 5, or older major versions).
  2. Verify if the web interface is exposed
    Confirm that Actual is running with its web server functionality enabled and accessible over HTTP/HTTPS. Path traversal only applies when the web endpoints are active. Check the application startup configuration or running processes to see if the web server component is running.
    Affected if The web interface is accessible (even on localhost) and the application version is prior to 26.5.0.
  3. Inspect web endpoint accessibility
    If Actual is running, test accessing a known web route (such as the main login or dashboard page) to confirm the web server is active. Note that even local-only access still constitutes a potential attack surface for the path traversal flaw.
    Affected if The web server responds to requests and the version is prior to 26.5.0.

A user is affected if they are running any version of Actual prior to 26.5.0 with the web interface enabled, regardless of whether it is exposed externally or accessible only locally.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Actual version 26.5.0 or later, which contains the patch for this path traversal vulnerability.

Recommended fix High confidence

26.5.0

  1. Backup your Actual personal finance data before performing any upgrade
  2. Upgrade to version 26.5.0 or later of Actual
  3. After upgrading, verify that the application runs without errors
  4. Test that file operations work correctly to confirm the path traversal fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43872 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-43872 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data