How severe is GHSA-m86m-5m44-pc93?

No CVSS score has been assigned to GHSA-m86m-5m44-pc93 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m86m-5m44-pc93?

GHSA-m86m-5m44-pc93 affects the following packages: grpc-ts-health-check (npm). Ecosystems affected: npm.

How do I fix GHSA-m86m-5m44-pc93?

Update grpc-ts-health-check to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m86m-5m44-pc93 is resolved across your whole dependency graph.

How do I detect GHSA-m86m-5m44-pc93 in my npm dependencies?

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

How do I mitigate GHSA-m86m-5m44-pc93 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-m86m-5m44-pc93 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m86m-5m44-pc93 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.

When was GHSA-m86m-5m44-pc93 published, and has it been updated?

GHSA-m86m-5m44-pc93 was published on September 3, 2020 and was last updated on August 31, 2020. 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

Denial of Service in grpc-ts-health-checkGHSA-m86m-5m44-pc93

GHSA-m86m-5m44-pc93 is a security vulnerability in grpc-ts-health-check. A fix is available for grpc-ts-health-check — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

grpc-ts-health-checknpm

314downloads / week

Description

Versions of grpc-ts-health-check prior to 2.0.0 are vulnerable to Denial of Service. The package exposes an API endpoint that may allow attackers to set the service's health status to failing. This can lead to Denial of Service as Kubernetes blocks traffic to services with a failing status.

Recommendation

Upgrade to version 2.0.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`grpc-ts-health-check`	all versions	2.0.0`npm install grpc-ts-health-check@2.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grpc-ts-health-check, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update grpc-ts-health-check to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m86m-5m44-pc93 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Versions of `grpc-ts-health-check` prior to 2.0.0 are vulnerable to Denial of Service. The package exposes an API endpoint that may allow attackers to set the service's health status to failing. This can lead to Denial of Service as Kubernetes blocks traffic to services with a failing status. ## Recommendation Upgrade to version 2.0.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-m86m-5m44-pc93 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works