TaffyDB can allow access to any data items in the DB

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2019-10790: 1.86% estimated exploitation activity in the next 30 days; percentile 79.27 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

TaffyDB allows attackers to forge adding additional properties into user-input processed by taffy which can allow access to any data items in the DB. Taffy sets an internal index for each data item in its DB. However, it is found that the internal index can be forged by adding additional properties into user-input. If index is found in the query, TaffyDB will ignore other query conditions and directly return the indexed data item. Moreover, the internal index is in an easily-guessable format (e.g., T000002R000001). As such, attackers can use this vulnerability to access any data items in the DB. Note: taffy and its successor package taffydb are not maintained.

Published by the source

19 Feb 2020, 16:43 UTC

Last modified by the source

10 Sep 2026, 03:48 UTC

Source last checked

26 Oct 2026, 12:17 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mxhp-79qh-mcx6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mxhp-79qh-mcx6

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

# Patch Next advisory brief: CVE-2019-10790

Advisory: TaffyDB can allow access to any data items in the DB
IDs: CVE-2019-10790, GHSA-mxhp-79qh-mcx6
Record: https://patchnext.com/advisories/cve-2019-10790 (revision 2, source checked 26 Oct 2026, 12:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm taffy: affected <= 2.6.2
- npm taffydb: affected <= 2.7.3

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on taffy, taffydb.
- 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-mxhp-79qh-mcx6 (OSV record GHSA-mxhp-79qh-mcx6 lists affected ranges: npm taffy >=0 =0 <=2.7.3)
- Verified: https://github.com/advisories/GHSA-mxhp-79qh-mcx6 (GitHub-reviewed advisory GHSA-mxhp-79qh-mcx6 lists affected ranges: npm taffy >=0 =0 <=2.7.3)

Commands are suggestions: review each one before running it.