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.6%, top 53% 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
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
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 / EcosystemFixed in / 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 rangeFixed inDependents
@grpc/grpc-js—1.14.4—

Weakness Classification(1)

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

Data Freshness Timeline

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

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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 53.1% of all scored CVEs.
What is the CVSS score of CVE-2026-48069?
CVE-2026-48069 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48069?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48069, 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-48069

Explore →

Is Your Infrastructure Affected by CVE-2026-48069?

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

Start Free Scan →Browse All CVEs