Vulnerability in @orpc/zod (CVE-2026-103918)
Summary
Vulnerability in @orpc/zod (CVE-2026-103918). Risk of unauthorized operations or information disclosure. Exploitable via ZodSmartCoercionPlugin. Mitigation: upgrade to 1.14.10 or later.
Original description
The description as published by the source.
Summary
ZodSmartCoercionPlugin and experimental_ZodSmartCoercionPlugin mishandle object keys that name Object.prototype members. Both coerce request input before validation, so any client that can reach a procedure whose input schema contains an object or a record can:
- replace the prototype of the coerced input object, and
- make a request fail with an unhandled
TypeErrorby sending a key such asconstructor.
This is the same class of bug as GHSA-4h5r-cv8j-4456 in @orpc/json-schema, in a different package.
This is not global prototype pollution
The global Object.prototype is never modified. No shared or global state is written, so other objects in the process, other requests, and other users are not affected.
What changes is the prototype of one object: the value the coercer returns for the request that carried the payload. That object is passed on to validation and to the procedure handler, then discarded when the request ends. An ordinary {} created anywhere else in the application is unaffected.
Details
1. __proto__ replaces the prototype of the coerced value
Coerced properties were collected into a plain {}, so newObj['__proto__'] = value triggers the inherited __proto__ setter instead of creating an own property. Verified on 1.14.8 against a record schema, in both plugins:
schema: z.record(z.string())
input: {"a":"1","__proto__":{"polluted":true}}
Object.keys(result) => ["a"] // the __proto__ entry is dro…
Source: NIST National Vulnerability Database 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-103918 has been found in @orpc/zod.
Attackers can target a specific entry point like ZodSmartCoercionPlugin over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade @orpc/zod to 1.14.10 or later.
If unsure, ask your IT team or search "@orpc/zod CVE-2026-103918" on the vendor's site.
CVE-2026-103918 (@orpc/zod) — CWE-915 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ZodSmartCoercionPlugin / experimental_ZodSmartCoercionPlugin / Object.prototype / TypeError
Patched: 1.14.10 — 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-915) exists in @orpc/zod. Attackers reach the vulnerable code path via ZodSmartCoercionPlugin without authentication.
Check the vendor advisory for the affected versions of @orpc/zod. Attack surface: ZodSmartCoercionPlugin / experimental_ZodSmartCoercionPlugin / Object.prototype / TypeError.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.14.10.
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 '@orpc/zod' . 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 '@orpc/zod' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@orpc/zodを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @orpc/zod to 1.14.10ステージング環境で 1.14.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。