When setting EntityOptions.apiPrefilter to a function, the filter is not applied to API requests for a resource by Id

Exploitation

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

CVSS

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

EPSS

• CVE-2023-35167: 0.55% estimated exploitation activity in the next 30 days; percentile 45.81 (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.

Impact If you used the apiPrefilter option of the @Entity decorator, by setting it to a function that returns a filter that prevents unauthorized access to data, an attacker who knows the id of an entity instance she is not authorized to access, can gain read, update and delete access to it. Patches The issue is fixed in version 0.20.6 Workarounds Set the apiPrefilter option to a filter object instead of a function. References If you're using a minor version < 0.20 and require a patch, please create an issue.

Published by the source

20 Jun 2023, 18:50 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 12:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7hh3-3x64-v2g9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7hh3-3x64-v2g9

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

# Patch Next advisory brief: CVE-2023-35167

Advisory: When setting EntityOptions.apiPrefilter to a function, the filter is not applied to API requests for a resource by Id
IDs: CVE-2023-35167, GHSA-7hh3-3x64-v2g9
Record: https://patchnext.com/advisories/cve-2023-35167 (revision 2, source checked 26 Oct 2026, 12:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: remult 0.20.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm remult: affected < 0.20.6; fixed in 0.20.6

## Suggested inspection (read-only)
- `npm ls remult --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 remult.
- 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-7hh3-3x64-v2g9 (OSV record GHSA-7hh3-3x64-v2g9 lists affected ranges: npm remult >=0 <0.20.6 (fixed))
- Verified: https://github.com/advisories/GHSA-7hh3-3x64-v2g9 (GitHub-reviewed advisory GHSA-7hh3-3x64-v2g9 lists affected ranges: npm remult >=0 <0.20.6)

Commands are suggestions: review each one before running it.