# CVE-2026-44483: RVF: Prototype pollution in @rvf/set-get reachable via @rvf/core preprocessFormData (HTTP form data)

> Attackers can pollute Object.prototype via form data, potentially leading to remote code execution or privilege escalation in React applications using RVF.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-c567-44rc-m5hq

## What is CVE-2026-44483?

CVE-2026-44483 is a high-severity code injection vulnerability in @rvf rvf, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RVF (formerly Remix Validated Form) provides easy form validation and state management for React. From 6.0.0 to before 6.0.4 and 7.0.2, 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. This vulnerability is fixed in 6.0.4 and 7.0.2.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

4 open source packages ship an affected version, including @rvf/set-get.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@rvf/set-get` | npm | From 6.0.0 | 6.0.4 |
| `@rvf/set-get` | npm | From 6.0.0 | 6.0.4 |
| `@rvf/set-get` | npm | From 7.0.0 | 7.0.2 |
| `@rvf/set-get` | npm | From 7.0.0 | 7.0.2 |

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

Upgrade @rvf/set-get to a fixed version for your release line: 6.0.4 or 7.0.2.

## Is CVE-2026-44483 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44483 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44483 is a high-severity code injection vulnerability in @rvf rvf, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44483 exists.

Affected packages and fixed versions:
- @rvf/set-get (npm): affected from 6.0.0; fixed in 6.0.4
- @rvf/set-get (npm): affected from 6.0.0; fixed in 6.0.4
- @rvf/set-get (npm): affected from 7.0.0; fixed in 7.0.2
- @rvf/set-get (npm): affected from 7.0.0; fixed in 7.0.2

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-44483/ (Markdown: https://insights.sbomify.com/CVE-2026-44483/index.md)
```

## Sources

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

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