CVE-2026-48069

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 43% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4, an invalid incoming compressed message can cause a client or server process that uses @grpc/grpc-js to crash. This issue is fixed in versions 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

Published

June 11, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit b6dcfc3cee9e (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit b6dcfc3cee9e)

https://github.com/grpc/grpc-node/commit/b6dcfc3cee9ef390e5869ebea5a8c5ae187720b9
github_commit Patch Available

commit b61c4d65953d (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit b61c4d65953d)

https://github.com/grpc/grpc-node/commit/b61c4d65953db85c2ae55b4b3cd98a4259dc87cb
github_commit Patch Available

commit b3f16094473b (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit b3f16094473b)

https://github.com/grpc/grpc-node/commit/b3f16094473b5c8f38b0955eafa4a19507127346
github_commit Patch Available

commit 4091bd902105 (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit 4091bd902105)

https://github.com/grpc/grpc-node/commit/4091bd902105f8fb655741758aee71418c48b5d5
github_commit Patch Available

commit 2fe55fd76a8b (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit 2fe55fd76a8b)

https://github.com/grpc/grpc-node/commit/2fe55fd76a8bb59eaab5f39e3552b5f84985a163
github_commit Patch Available

commit 2375eadcc52c (grpc/grpc-node)

Patch available: grpc/grpc-node @grpc/[email protected] (contains commit 2375eadcc52c)

https://github.com/grpc/grpc-node/commit/2375eadcc52ca2b1ef55288bcd6355168b02706c

Vendor Advisories for CVE-2026-48069(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17859728432026-08-10redhat
redhatrhdh/rhdh-hub-rhel9:17854116522026-08-03redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17853326942026-07-29redhat

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
@grpc/grpc-js—
  • every version up to 1.9.16: fixed in 1.9.16
  • 1.10.0 up to 1.10.12: fixed in 1.10.12
  • 1.11.0 up to 1.11.4: fixed in 1.11.4
  • 1.12.0 up to 1.12.7: fixed in 1.12.7
  • 1.13.0 up to 1.13.5: fixed in 1.13.5
  • 1.14.0 up to 1.14.4: fixed in 1.14.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 22× 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.

Showing the most recent 100 of 141 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48069?
CVE-2026-48069 is a high vulnerability published on June 11, 2026. @grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4, an invalid incoming compressed message can cause a client or server process that uses @grpc/grpc-js to crash. This issue is fixed in…
When was CVE-2026-48069 disclosed?
CVE-2026-48069 was first published on June 11, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48069 actively exploited?
CVE-2026-48069 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48069?
CVE-2026-48069 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48069?
A fix for CVE-2026-48069 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48069 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48069?

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

Book a Demo →Browse All CVEs