How severe is GHSA-5375-pq7m-f5r2?

GHSA-5375-pq7m-f5r2 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5375-pq7m-f5r2?

GHSA-5375-pq7m-f5r2 affects the following packages: @grpc/grpc-js (npm), @grpc/grpc-js (npm), @grpc/grpc-js (npm), @grpc/grpc-js (npm), @grpc/grpc-js (npm), @grpc/grpc-js (npm). Ecosystems affected: npm.

How do I fix GHSA-5375-pq7m-f5r2?

Update @grpc/grpc-js to 1.9.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5375-pq7m-f5r2 is resolved across your whole dependency graph.

How do I detect GHSA-5375-pq7m-f5r2 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @grpc/grpc-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5375-pq7m-f5r2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-5375-pq7m-f5r2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5375-pq7m-f5r2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5375-pq7m-f5r2?

GHSA-5375-pq7m-f5r2 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 58th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5375-pq7m-f5r2?

GHSA-5375-pq7m-f5r2 is classified as CWE-248 (CWE-248). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5375-pq7m-f5r2 published, and has it been updated?

GHSA-5375-pq7m-f5r2 was published on June 11, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

@grpc/grpc-js: A malformed request can cause a server crashGHSA-5375-pq7m-f5r2

HIGH

GHSA-5375-pq7m-f5r2 is a high-severity (CVSS 7.5) CWE-248 vulnerability in @grpc/grpc-js. A fix is available for @grpc/grpc-js — see the affected versions and patch details below.

Also known asCVE-2026-48068

Published

Jun 11, 2026

Updated

Sep 10, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5375-pq7m-f5r2.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-5375-pq7m-f5r2 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

6 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@grpc/grpc-jsnpm

60.2Mdownloads / week

Description

@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 HTTP/2 stream initiation can cause a server process created using @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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@grpc/grpc-js`	all versions	1.9.16`npm install @grpc/grpc-js@1.9.16`
📦npm	`@grpc/grpc-js`	≥ 1.10.0&&< 1.10.12	1.10.12`npm install @grpc/grpc-js@1.10.12`
📦npm	`@grpc/grpc-js`	≥ 1.11.0&&< 1.11.4	1.11.4`npm install @grpc/grpc-js@1.11.4`
📦npm	`@grpc/grpc-js`	≥ 1.12.0&&< 1.12.7	1.12.7`npm install @grpc/grpc-js@1.12.7`
📦npm	`@grpc/grpc-js`	≥ 1.13.0&&< 1.13.5	1.13.5`npm install @grpc/grpc-js@1.13.5`
📦npm	`@grpc/grpc-js`	≥ 1.14.0&&< 1.14.4	1.14.4`npm install @grpc/grpc-js@1.14.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @grpc/grpc-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @grpc/grpc-js to 1.9.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5375-pq7m-f5r2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A flaw was found in @grpc/grpc-js. An invalid incoming HTTP/2 stream initiation can cause a server process to crash. This affects all servers created using @grpc/grpc-js. There is no workaround.

Workaround published by Red Hat

Upgrade to @grpc/grpc-js 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, or 1.14.4. There is no workaround for this vulnerability.

Source: Red Hat security advisory for GHSA-5375-pq7m-f5r2 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`rh-podman-desktop-0:1.1.2-1.el10_2`	RHSA-2026:57590
Red Hat Ansible Automation Platform 2.1	`ansible-automation-platform/automation-portal:1785854226`	RHSA-2026:50850
Red Hat Ansible Automation Platform 2.2	`ansible-automation-platform/automation-portal:1785857303`	RHSA-2026:50839
Red Hat Ansible Automation Platform 2.2	`ansible-automation-platform/bootc-automation-portal-rhel9:1786006573`	RHSA-2026:51162
Red Hat Developer Hub 1.10	`rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend:1785332487`	RHSA-2026:48126
Red Hat Developer Hub 1.10	`rhdh/rhdh-hub-rhel9:1785411652`	RHSA-2026:49642
Red Hat Developer Hub 1.9	`rhdh/rhdh-hub-rhel9:1785972843`	RHSA-2026:52768
Red Hat OpenShift Dev Spaces 3.30	`devspaces/code-rhel9:1787762793`	RHSA-2026:62260

Frequently Asked Questions

### Impact An invalid incoming HTTP/2 stream initiation can cause a server process to crash. This affects all servers created using @grpc/grpc-js. ### Patches The following version have fixes for this vulnerability: - 1.9.16 - 1.10.12 - 1.11.4 - 1.12.7 - 1.13.5 - 1.14.4 ### Workarounds There is no workaround.