CVE-2026-48819: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in hey-api openapi-ts
Hey 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.
AI Analysis
Technical Summary
Hey API's openapi-ts package versions before 0.97.3 contain a prototype pollution vulnerability (CWE-1321) in the buildClientParams function. This function writes unknown slot-prefixed keys (e.g., $query_) directly to parameter objects, permitting an attacker to supply a key like $query___proto__ that sets params.query.__proto__ to an attacker-controlled value. This manipulation exposes inherited attacker-controlled keys during for..in iteration, potentially affecting application behavior relying on these parameters. The vulnerability is resolved in version 0.97.3.
Potential Impact
An attacker can modify the prototype of parameter objects, causing inherited properties to be attacker-controlled. This may lead to unexpected behavior in applications using the affected SDKs, including potential information disclosure or logic manipulation. The CVSS score of 4.8 reflects a medium impact with low confidentiality and integrity impact and no availability impact.
Mitigation Recommendations
Upgrade to hey-api openapi-ts version 0.97.3 or later, where this prototype pollution vulnerability is fixed. No other mitigation or temporary workaround is documented. Patch status is not explicitly stated but the vendor has fixed the issue in 0.97.3, so updating to this version or newer is the recommended remediation.
CVE-2026-48819: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in hey-api openapi-ts
Description
Hey 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.
CVSS v3.1
Score 4.8medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Hey API's openapi-ts package versions before 0.97.3 contain a prototype pollution vulnerability (CWE-1321) in the buildClientParams function. This function writes unknown slot-prefixed keys (e.g., $query_) directly to parameter objects, permitting an attacker to supply a key like $query___proto__ that sets params.query.__proto__ to an attacker-controlled value. This manipulation exposes inherited attacker-controlled keys during for..in iteration, potentially affecting application behavior relying on these parameters. The vulnerability is resolved in version 0.97.3.
Potential Impact
An attacker can modify the prototype of parameter objects, causing inherited properties to be attacker-controlled. This may lead to unexpected behavior in applications using the affected SDKs, including potential information disclosure or logic manipulation. The CVSS score of 4.8 reflects a medium impact with low confidentiality and integrity impact and no availability impact.
Mitigation Recommendations
Upgrade to hey-api openapi-ts version 0.97.3 or later, where this prototype pollution vulnerability is fixed. No other mitigation or temporary workaround is documented. Patch status is not explicitly stated but the vendor has fixed the issue in 0.97.3, so updating to this version or newer is the recommended remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-22T20:57:10.976Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b5eae2d1edb114c7fb31e
Added to database: 07/18/2026, 11:08:30 UTC
Last enriched: 07/18/2026, 11:53:45 UTC
Last updated: 07/18/2026, 13:13:14 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.