Vulnerability in @hey-api/openapi-ts (CVE-2026-48819)
Summary
Vulnerability in @hey-api/openapi-ts (CVE-2026-48819). Risk of unauthorized operations or information disclosure. Exploitable via GET /search. Mitigation: upgrade to 0.97.3 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48819 has been found in @hey-api/openapi-ts.
Attackers can target a specific entry point like GET /search over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade @hey-api/openapi-ts to 0.97.3 or later.
If unsure, ask your IT team or search "@hey-api/openapi-ts CVE-2026-48819" on the vendor's site.
CVE-2026-48819 (@hey-api/openapi-ts) — CWE-1321 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /search / params.gen.ts / params.query / __proto__
Patched: 0.97.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in @hey-api/openapi-ts. Attackers reach the vulnerable code path via GET /search without authentication.
Check the vendor advisory for the affected versions of @hey-api/openapi-ts. Attack surface: GET /search / params.gen.ts / params.query / __proto__.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.97.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /search requests with malformed payloads or SQL meta-characters. Run grep -r '@hey-api/openapi-ts' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@hey-api/openapi-ts' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@hey-api/openapi-tsを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /search' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /searchへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @hey-api/openapi-ts to 0.97.3ステージング環境で 0.97.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /search on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com