# CVE-2026-50179: Actual: CSV Formula Injection in Transaction Export via Imported Payee/Notes Fields

> Attackers can inject malicious formulas into CSV exports via imported fields, leading to data exfiltration when opened in spreadsheet software.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-xqjm-27pc-rvwm

## What is CVE-2026-50179?

CVE-2026-50179 is a medium-severity vulnerability in actualbudget actual, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Actual is a local-first personal finance tool. Prior to 26.6.0, exportToCSV and exportQueryToCSV in packages/loot-core/src/server/transactions/export/export-to-csv.ts pass user-controlled Payee, Notes, Account, and Category strings to csv-stringify with no cast callback and no formula-prefix neutralization. Strings that begin with equals sign, plus, minus, at sign, tab, or carriage return survive verbatim into the exported CSV, and when a recipient opens the file in Excel, LibreOffice Calc, or Google Sheets, the strings are interpreted as formulas, enabling transaction data exfiltration and attacker-chosen spreadsheet display values. This issue is fixed in version 26.6.0.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

## Which versions are affected by CVE-2026-50179?

2 open source packages ship an affected version, including @actual-app/web.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@actual-app/web` | npm | All versions | 26.6.0 |
| `@actual-app/web` | npm | All versions | 26.6.0 |

## How do I fix CVE-2026-50179?

Upgrade @actual-app/web to 26.6.0 or later.

## Is CVE-2026-50179 being exploited?

There is no known exploitation of CVE-2026-50179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50179 and fix it if it is affected.

What it is: CVE-2026-50179 is a medium-severity vulnerability in actualbudget actual, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-50179 in the wild and no public exploit code.

Affected packages and fixed versions:
- @actual-app/web (npm): affected all versions; fixed in 26.6.0
- @actual-app/web (npm): affected all versions; fixed in 26.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50179/ (Markdown: https://insights.sbomify.com/CVE-2026-50179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50179
- OSV: https://osv.dev/vulnerability/CVE-2026-50179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50179/
Summaries are generated and may contain mistakes; the official description above is the record.