{"answers":{"affected":"4 open source packages ship an affected version, including @trpc/server.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68130 exists.","fix":"Upgrade @trpc/server to a fixed version for your release line: 10.45.3 or 11.8.0.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-68130 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68130 exists.\n\nAffected packages and fixed versions:\n- @trpc/server (npm): affected from 10.27.0; fixed in 10.45.3\n- @trpc/server (npm): affected from 10.27.0; fixed in 10.45.3\n- @trpc/server (npm): affected from 11.0.0; fixed in 11.8.0\n- @trpc/server (npm): affected from 11.0.0; fixed in 11.8.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68130/ (Markdown: https://insights.sbomify.com/CVE-2025-68130/index.md)","id":"CVE-2025-68130","markdown":"https://insights.sbomify.com/CVE-2025-68130/index.md","name":"CVE-2025-68130","record":{"aliases":["GHSA-43p4-m455-4f4j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"tRPC server library","requires_auth":"low_privilege","summary":"Prototype pollution in tRPC's Next.js adapter allows attackers to bypass authorization or cause denial of service via crafted FormData.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"tRPC has possible prototype pollution in `experimental_nextAppDirCaller`","id":"CVE-2025-68130","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2025"},"n_packages":4,"n_references":1,"next":{"headline":"CBORDecoder reuse can leak shareable values across decode calls","id":"CVE-2025-68131"},"packages":[{"ecosystem":"npm","fixed":["10.45.3"],"introduced":["10.27.0"],"last_affected":[],"package":"@trpc/server","purl":null,"source":"GHSA-43p4-m455-4f4j"},{"ecosystem":"npm","fixed":["10.45.3"],"introduced":["10.27.0"],"last_affected":[],"package":"@trpc/server","purl":"pkg:npm/%40trpc/server","source":"GHSA-43p4-m455-4f4j"},{"ecosystem":"npm","fixed":["11.8.0"],"introduced":["11.0.0"],"last_affected":[],"package":"@trpc/server","purl":null,"source":"GHSA-43p4-m455-4f4j"},{"ecosystem":"npm","fixed":["11.8.0"],"introduced":["11.0.0"],"last_affected":[],"package":"@trpc/server","purl":"pkg:npm/%40trpc/server","source":"GHSA-43p4-m455-4f4j"}],"prev":{"headline":"Auth0-PHP SDK has Improper Audience Validation","id":"CVE-2025-68129"},"products":["trpc"],"published":"2025-12-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-16","vendors":["trpc"]},"summary":"Prototype pollution in tRPC's Next.js adapter allows attackers to bypass authorization or cause denial of service via crafted FormData.","url":"https://insights.sbomify.com/CVE-2025-68130/"}