Vulnerability in @ranfdev/deepobj (CVE-2026-46509)
Summary
Vulnerability in @ranfdev/deepobj (CVE-2026-46509). Data can be tampered with by attackers. Exploitable via __proto__. Mitigation: upgrade to 1.0.3 or later.
Original description
The description as published by the source.
Impact
Prototype pollution is possible when property paths contain __proto__/constructor/prototype. The property path must not be exposed as user input.
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-46509 has been found in @ranfdev/deepobj.
Attackers can target a specific entry point like __proto__ over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade @ranfdev/deepobj to 1.0.3 or later.
If unsure, ask your IT team or search "@ranfdev/deepobj CVE-2026-46509" on the vendor's site.
CVE-2026-46509 (@ranfdev/deepobj) — CWE-1321 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: __proto__ / constructor / prototype
Patched: 1.0.3 — 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 @ranfdev/deepobj. Attackers reach the vulnerable code path via __proto__ without authentication.
Check the vendor advisory for the affected versions of @ranfdev/deepobj. Attack surface: __proto__ / constructor / prototype.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 1.0.3.
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 '@ranfdev/deepobj' . 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 '@ranfdev/deepobj' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@ranfdev/deepobjを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @ranfdev/deepobj to 1.0.3ステージング環境で 1.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com