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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m86m-5m44-pc93 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.

How does O3 Security protect against GHSA-m86m-5m44-pc93?

O3 pinpoints whether GHSA-m86m-5m44-pc93 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-m86m-5m44-pc93

GHSA-m86m-5m44-pc93 is a security vulnerability in grpc-ts-health-check. O3 Security confirms whether GHSA-m86m-5m44-pc93 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in grpc-ts-health-check

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

📦grpc-ts-health-check

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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.
How O3 protects you
O3 pinpoints whether GHSA-m86m-5m44-pc93 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m86m-5m44-pc93. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-m86m-5m44-pc93 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works