CVE-2026-28794
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedoRPC is an tool that helps build APIs that are end-to-end type-safe and adhere to OpenAPI standards. Prior to version 1.13.6, a prototype pollution vulnerability exists in the RPC JSON deserializer of the @orpc/client package. The vulnerability allows unauthenticated, remote attackers to inject arbitrary properties into the global Object.prototype. Because this pollution persists for the lifetime of the Node.js process and affects all objects, it can lead to severe security breaches, including authentication bypass, denial of service, and potentially Remote Code Execution. This issue has been patched in version 1.13.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA prototype pollution vulnerability exists in the RPC JSON deserializer of the @orpc/client package prior to version 1.13.6. The flaw allows unauthenticated attackers to inject arbitrary properties into the global Object.prototype through malicious JSON input during RPC communication. Because this pollution persists for the entire Node.js process lifetime and affects all objects, it can lead to authentication bypass, denial of service, and potentially remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.13.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed @orpc/client versionRun 'npm list @orpc/client' in your project directory, or inspect package.json dependencies to find the exact version number installedAffected if The version shown is less than 1.13.6
-
Confirm RPC endpoint exposureReview your application code to identify where @orpc/client is used to handle incoming RPC requests, particularly any endpoints that accept JSON input from clients or external servicesAffected if Your application exposes RPC endpoints that process JSON data from untrusted sources
-
Check for input validationExamine your RPC handlers and middleware to determine whether incoming JSON payloads are validated or sanitized before deserializationAffected if No validation or sanitization is performed on JSON input before it reaches the orpc deserializer
-
Test for prototype pollutionSend a test RPC request with a JSON payload containing '__proto__' or 'constructor.prototype' with an arbitrary property value, then inspect Object.prototype to see if the property was injectedAffected if The injected property appears in Object.prototype after the request is processed
You are affected if you are running @orpc/client version below 1.13.6 and your RPC endpoints accept untrusted JSON input that is not validated before deserialization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.13.6
Upgrade @orpc/client to version 1.13.6 or later to patch the vulnerable JSON deserializer. Verify all RPC endpoints validate and sanitize JSON input to prevent prototype pollution even after patching.
1.13.6
- Identify all projects using the @orpc/client package in your dependency tree
- Run npm update @orpc/client or yarn upgrade @orpc/client to update to the latest version
- Alternatively, manually update the version in package.json to ^1.13.6 or higher and run npm install
- Verify the installed version is 1.13.6 or later with npm list @orpc/client
- After updating, restart any running Node.js processes to ensure the patched code is loaded
- Audit your application code to check for any prototype pollution side effects that may have been introduced prior to the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28794 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data