Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

@rvf/set-get has a prototype pollution issue that's reachable via @rvf/core preprocessFormData (HTTP form data)

CVE-2026-44483GHSA-c567-44rc-m5hq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@rvf/set-get 7.0.2, 6.0.4), 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

  • npm @rvf/set-get

    Affected
    >= 7.0.0, < 7.0.2>= 6.0.0, < 6.0.4
    Fixed in
    7.0.2, 6.0.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS
  • CVE-2026-44483: 0.36% estimated exploitation activity in the next 30 days; percentile 29.75 (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 setPath in @rvf/set-get (used by @rvf/core to flatten incoming form data into a nested object) does not block the keys proto, constructor, or prototype when walking a path. Because field names in submitted form data are passed directly to setPath via preprocessFormData (and through parseFormData / validate), an attacker who can submit a form to a Remix / React Router app using the library can set arbitrary properties on Object.prototype of the running server process. This is a default-reachable prototype pollution primitive: no special configuration is required. Any endpoint that accepts a form via parseFormData or runs a validator created with createValidator is affected. Affected versions - @rvf/set-get < 7.0.2 (7.x line) - @rvf/set-get < 6.0.4 (6.x line) Reached through @rvf/core versions that depend on a vulnerable @rvf/set-get (current 8.1.0 resolves to 7.0.1 without the override). Patched - @rvf/set-get 7.0.2 - @rvf/set-get 6.0.4 The fix adds a REJECTKEYS blocklist…

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

    Amended from ghsa record GHSA-c567-44rc-m5hq

  2. Revision 1 · created ·

    Published from osv record GHSA-c567-44rc-m5hq

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-44483

Advisory: @rvf/set-get has a prototype pollution issue that's reachable via @rvf/core preprocessFormData (HTTP form data)
IDs: CVE-2026-44483, GHSA-c567-44rc-m5hq
Record: https://patchnext.com/advisories/cve-2026-44483 (revision 2, source checked 26 Oct 2026, 12:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @rvf/set-get 7.0.2, 6.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @rvf/set-get: affected >= 7.0.0, < 7.0.2; >= 6.0.0, < 6.0.4; fixed in 7.0.2, 6.0.4

## Suggested inspection (read-only)
- `npm ls @rvf/set-get --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 @rvf/set-get.
- 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-c567-44rc-m5hq (OSV record GHSA-c567-44rc-m5hq lists affected ranges: npm @rvf/set-get >=7.0.0 =6.0.0 <6.0.4 (fixed))
- Verified: https://github.com/advisories/GHSA-c567-44rc-m5hq (GitHub-reviewed advisory GHSA-c567-44rc-m5hq lists affected ranges: npm @rvf/set-get >=7.0.0 =6.0.0 <6.0.4)

Commands are suggestions: review each one before running it.

Loading voting…