How severe is GHSA-f596-whhp-79r4?

GHSA-f596-whhp-79r4 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-f596-whhp-79r4?

GHSA-f596-whhp-79r4 affects the following packages: @grpc/grpc-js (npm), @grpc/grpc-js (npm). Ecosystems affected: npm.

How do I fix GHSA-f596-whhp-79r4?

Update @grpc/grpc-js to 1.13.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f596-whhp-79r4 is resolved across your whole dependency graph.

How do I detect GHSA-f596-whhp-79r4 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-f596-whhp-79r4 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-f596-whhp-79r4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f596-whhp-79r4 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-f596-whhp-79r4?

GHSA-f596-whhp-79r4 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 16th 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-f596-whhp-79r4?

GHSA-f596-whhp-79r4 is classified as CWE-550 (CWE-550). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f596-whhp-79r4 published, and has it been updated?

GHSA-f596-whhp-79r4 was published on September 30, 2026 and was last updated on September 30, 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

LOW severity

@grpc/grpc-js: The server transmits some error messages thrown by method handlers to the client in status messagesGHSA-f596-whhp-79r4

LOWFix: grpc/grpc-node@350de32

GHSA-f596-whhp-79r4 is a low-severity (CVSS 3.7) CWE-550 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-101915

Published

Sep 30, 2026

Updated

Sep 30, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-f596-whhp-79r4.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-f596-whhp-79r4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Real-World Exposure

2 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

38.1Mdownloads / week

Description

Impact

If an application method handler crashes, the error message is included in the status message sent to the client. This can leak to the client any sensitive data that may be included in the error message. This impacts anyone using @grpc/grpc-js to run servers.

Patches

This vulnerability is fixed in 1.13.6 and 1.14.5.

Workarounds

This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@grpc/grpc-js`	all versions	1.13.6`npm install @grpc/grpc-js@1.13.6`
📦npm	`@grpc/grpc-js`	≥ 1.14.0&&< 1.14.5	1.14.5`npm install @grpc/grpc-js@1.14.5`

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.13.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f596-whhp-79r4 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.

Frequently Asked Questions

### Impact If an application method handler crashes, the error message is included in the status message sent to the client. This can leak to the client any sensitive data that may be included in the error message. This impacts anyone using `@grpc/grpc-js` to run servers. ### Patches This vulnerability is fixed in 1.13.6 and 1.14.5. ### Workarounds This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.