Vulnerability in @rvf/set-get (CVE-2026-44483)
Summary
Vulnerability in @rvf/set-get (CVE-2026-44483). Data can be tampered with by attackers. Exploitable via setPath. Mitigation: upgrade to 6.0.4 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44483 has been found in @rvf/set-get.
Attackers can target a specific entry point like setPath over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade @rvf/set-get to 6.0.4 or later.
If unsure, ask your IT team or search "@rvf/set-get CVE-2026-44483" on the vendor's site.
CVE-2026-44483 (@rvf/set-get) — CWE-1321 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: setPath / __proto__ / constructor / prototype
Patched: 6.0.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in @rvf/set-get. Attackers reach the vulnerable code path via setPath without authentication.
Check the vendor advisory for the affected versions of @rvf/set-get. Attack surface: setPath / __proto__ / constructor / prototype.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 6.0.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@rvf/set-get' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@rvf/set-get' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@rvf/set-getを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @rvf/set-get to 6.0.4ステージング環境で 6.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com