CVE-2025-68130

HIGHNVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-203822 (ENISA EUVD) · GHSA-43p4-m455-4f4j (GitHub Security Advisories)Source: ENISA EUVD

8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
69
EG Risk 69/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 16, 2025

Last Modified

October 13, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Possible prototype pollution in `experimental_nextAppDirCaller` · Advisory · trpc/trpc · GitHub

https://github.com/trpc/trpc/security/advisories/GHSA-43p4-m455-4f4j

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@trpc/server @ 10.45.3 (fixes >= 10.27.0, < 10.45.3)—ghsa
npm@trpc/server @ 11.8.0 (fixes >= 11.0.0, < 11.8.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@trpc/server—
  • 10.27.0 up to 10.45.3: fixed in 10.45.3
  • 11.0.0 up to 11.8.0: fixed in 11.8.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 227 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-01 08:01 UTCGHSA enrichmentGHSA-43p4-m455-4f4j · GitHub severity HIGH
  4. 2026-11-01 08:01 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-29 07:08 UTCEG score recompute
  9. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-25 16:06 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-22 11:55 UTCEG score recompute
  18. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-20 10:00 UTCEG score recompute
  21. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-10-18 05:18 UTCEG score recompute
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 74 more
  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-12 16:47 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-11 20:22 UTCEG score recompute
  7. 2026-10-11 18:34 UTCEG score recompute
  8. 2026-10-11 15:09 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-03 17:19 UTCOSV refresh
  18. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  27. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  30. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  32. 2026-09-14 07:50 UTCOSV refresh
  33. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  35. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  36. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  38. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  40. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  41. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  42. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  43. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  44. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  46. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  48. 2026-08-26 09:13 UTCOSV refresh
  49. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  50. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  53. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  54. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  55. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  56. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  57. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  58. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  60. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  61. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  62. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  63. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  64. 2026-08-09 23:34 UTCEG score recompute
  65. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  66. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  67. 2026-08-08 06:20 UTCEG score recompute
  68. 2026-08-07 16:27 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  69. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  70. 2026-08-06 08:51 UTCEG score recompute
  71. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  72. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  73. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  74. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 26th percentile

Frequently asked(5)

What is CVE-2025-68130?
CVE-2025-68130 is a high-severity vulnerability; its CVE record was published on December 16, 2025. 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…
When was the CVE record for CVE-2025-68130 published?
The CVE record for CVE-2025-68130 was published on December 16, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2025-68130 actively exploited?
CVE-2025-68130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68130?
CVE-2025-68130 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2025-68130?
A fix for CVE-2025-68130 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68130

Explore →

Is Your Infrastructure Affected by CVE-2025-68130?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.