# CVE-2025-68130: tRPC has possible prototype pollution in `experimental_nextAppDirCaller`

> Prototype pollution in tRPC's Next.js adapter allows attackers to bypass authorization or cause denial of service via crafted FormData.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-43p4-m455-4f4j

## What is CVE-2025-68130?

CVE-2025-68130 is a high-severity vulnerability in trpc, published on 16 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

tRPC allows users to build and consume fully typesafe APIs without schemas or code generation. Starting in version 10.27.0 and prior to versions 10.45.3 and 11.8.0, a 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. Note that this vulnerability is only present when using `experimental_caller` / `experimental_nextAppDirCaller`. Versions 10.45.3 and 11.8.0 fix the issue.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-68130?

4 open source packages ship an affected version, including @trpc/server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@trpc/server` | npm | From 10.27.0 | 10.45.3 |
| `@trpc/server` | npm | From 10.27.0 | 10.45.3 |
| `@trpc/server` | npm | From 11.0.0 | 11.8.0 |
| `@trpc/server` | npm | From 11.0.0 | 11.8.0 |

## How do I fix CVE-2025-68130?

Upgrade @trpc/server to a fixed version for your release line: 10.45.3 or 11.8.0.

## Is CVE-2025-68130 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68130 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68130 and fix it if it is affected.

What it is: CVE-2025-68130 is a high-severity vulnerability in trpc, published on 16 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68130 exists.

Affected packages and fixed versions:
- @trpc/server (npm): affected from 10.27.0; fixed in 10.45.3
- @trpc/server (npm): affected from 10.27.0; fixed in 10.45.3
- @trpc/server (npm): affected from 11.0.0; fixed in 11.8.0
- @trpc/server (npm): affected from 11.0.0; fixed in 11.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68130/ (Markdown: https://insights.sbomify.com/CVE-2025-68130/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68130
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68130
- OSV: https://osv.dev/vulnerability/CVE-2025-68130

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68130/
Summaries are generated and may contain mistakes; the official description above is the record.
