CVE-2026-48819

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
4.8
EG Score
4.8(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit da321a1529eb (hey-api/hey-api)

Patch available: hey-api/hey-api 2026-06-22 (contains commit da321a1529eb)

https://github.com/hey-api/hey-api/commit/da321a1529eb3c90d2109da870f514b915a60169
github_commit Patch Available

commit 023909137a15 (hey-api/hey-api)

Patch available: hey-api/hey-api 2026-06-22 (contains commit 023909137a15)

https://github.com/hey-api/hey-api/commit/023909137a15eff9c0263d3bcd116140076b214f
github Patch Available🟡 PoC Available

`buildClientParams` template: prototype chain substitution via unknown `$<slot>___proto__` key · Advisory · hey-api/hey-api · GitHub

https://github.com/hey-api/hey-api/security/advisories/GHSA-hhx9-57xq-r5rw

Vendor Advisories for CVE-2026-48819(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@hey-api/openapi-ts—0.97.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 16:16 UTCEG score recompute
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 11:26 UTCEG score recompute
  5. 2026-08-23 09:42 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 08:00 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 06:18 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 04:36 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-19 01:01 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 23:18 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 16:45 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 15:03 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 13:20 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 11:38 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 41 more
  1. 2026-08-12 09:56 UTCEG score recompute
  2. 2026-08-11 08:12 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-10 06:30 UTCEG score recompute
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-09 04:48 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-08 03:06 UTCEG score recompute
  9. 2026-08-07 01:24 UTCEG score recompute
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 23:42 UTCEG score recompute
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-04 22:00 UTCEG score recompute
  14. 2026-08-04 15:10 UTCEPSS rescore
  15. 2026-08-04 10:39 UTCEPSS rescore
  16. 2026-08-02 17:33 UTCEG score recompute
  17. 2026-08-02 02:27 UTCEPSS rescore
  18. 2026-08-01 15:51 UTCEG score recompute
  19. 2026-08-01 04:16 UTCEPSS rescore
  20. 2026-07-31 14:08 UTCEG score recompute
  21. 2026-07-30 16:28 UTCEPSS rescore
  22. 2026-07-30 12:16 UTCEG score recompute
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-29 10:19 UTCEG score recompute
  25. 2026-07-28 15:37 UTCEPSS rescore
  26. 2026-07-28 08:36 UTCEG score recompute
  27. 2026-07-27 06:54 UTCEG score recompute
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 05:10 UTCEG score recompute
  30. 2026-07-25 14:18 UTCEPSS rescore
  31. 2026-07-24 14:18 UTCEPSS rescore
  32. 2026-07-23 14:18 UTCEPSS rescore
  33. 2026-07-23 03:18 UTCEG score recompute
  34. 2026-07-22 14:08 UTCEPSS rescore
  35. 2026-07-21 15:25 UTCEPSS rescore
  36. 2026-07-20 17:08 UTCEPSS rescore
  37. 2026-07-19 14:31 UTCEPSS rescore
  38. 2026-07-19 14:31 UTCEPSS rescore
  39. 2026-07-19 03:52 UTCEG score recompute
  40. 2026-07-19 02:29 UTCEPSS rescore
  41. 2026-07-01 21:02 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48819?
CVE-2026-48819 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-48819 disclosed?
CVE-2026-48819 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48819 actively exploited?
CVE-2026-48819 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.1% of all scored CVEs.
What is the CVSS score of CVE-2026-48819?
CVE-2026-48819 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-48819?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48819, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48819

Explore →

Is Your Infrastructure Affected by CVE-2026-48819?

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

Start Free Scan →Browse All CVEs