Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.5amended

tRPC has possible prototype pollution in experimental_nextAppDirCaller

CVE-2025-68130GHSA-43p4-m455-4f4j

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@trpc/server 11.8.0, 10.45.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @trpc/server

    Affected
    >= 10.27.0, < 10.45.3>= 11.0.0, < 11.8.0
    Fixed in
    10.45.3, 11.8.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L · score source
EPSS
  • CVE-2025-68130: 0.40% estimated exploitation activity in the next 30 days; percentile 33.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Note that this vulnerability is only present when using experimentalcaller / experimentalnextAppDirCaller. Summary A Prototype Pollution vulnerability exists in @trpc/server's formDataToObject function, which is used by the Next.js App Router adapter. An attacker can pollute Object.prototype by submitting specially crafted FormData field names, potentially leading to authorization bypass, denial of service, or other security impacts. Affected Versions - Package: @trpc/server - Affected Versions: =10.27.0 - Vulnerable Component: formDataToObject() in src/unstable-core-do-not-import/http/formDataToObject.ts Vulnerability Details Root Cause The set() function in formDataToObject.ts recursively processes FormData field names containing bracket/dot notation (e.g., user[name], user.address.city) to create nested objects. However, it does not validate or sanitize dangerous keys like proto, constructor, or prototype. Vulnerable Code Attack Vector When a user submits a form to a tRPC mutation…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-43p4-m455-4f4j

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-43p4-m455-4f4j

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68130

Advisory: tRPC has possible prototype pollution in `experimental_nextAppDirCaller`
IDs: CVE-2025-68130, GHSA-43p4-m455-4f4j
Record: https://patchnext.com/advisories/cve-2025-68130 (revision 3, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @trpc/server 11.8.0, 10.45.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @trpc/server: affected >= 10.27.0, < 10.45.3; >= 11.0.0, < 11.8.0; fixed in 10.45.3, 11.8.0

## Suggested inspection (read-only)
- `npm ls @trpc/server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @trpc/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-43p4-m455-4f4j (OSV record GHSA-43p4-m455-4f4j lists affected ranges: npm @trpc/server >=10.27.0 =11.0.0 <11.8.0 (fixed))
- Verified: https://github.com/advisories/GHSA-43p4-m455-4f4j (GitHub-reviewed advisory GHSA-43p4-m455-4f4j lists affected ranges: npm @trpc/server >=10.27.0 =11.0.0 <11.8.0)

Commands are suggestions: review each one before running it.

Loading voting…